The dashboard app doesn't have much documentation - it took me a while to figure out I needed to install the Google Cloud SDK to do anything with it. It would be nice to have some basic setup instructions documented.

As we've found in rust-lang/rust#36705, jemalloc has abysmal fork performance in some kernel configurations, notably on recent Ubuntu versions.

Even on good configurations system default allocator has about 20% better fork performance than jemalloc.

This can be done in documentation, by adding the 2 lines described in https://doc.rust-lang.org/nightly/book/custom-alloc

This is something that hasn't been super clear to me, and I haven't really seen it discussed anywhere ever.

The corpus

• can end up getting sizable (see also #163)
• often isn't human readable

Committing it to the project-being-fuzzed's repo seems like it could add a bunch of git overhead and even make merges difficult.

But, it is needed to "pick up where you left off" when doing time

Per #2, deque cannot be analyzed symbolically. Tentative plan is to implement a "dumb" version on top of a generic list: https://github.com/pschanely/CrossHair/blob/56ce14ee44c1103121c483f479d3d1a5a4bd3438/crosshair/simplestructs.py#L57

Currently, the user has 2 to create a .tar.gz archive of the corpus in order to submit it with --seed arg.

To save this step --seed arg should also take a directory name. If it's a directory, it does the creating of .tar.gz itself.

Also, should validate that there are no subdirectories (which is probably a mistake) and that there is at least 1 file.

It would be helpful to have a table (perhaps in the readme) summarizing the pros and cons of each target so that users can decide which to use based on application which is best suited.