Comment 14 for bug 513044

> Max, yeah 'hang' doesn't always mean the process has stopped entirely.

  Hey spm. I know that, but *this particular bug* is about a hard hang that causes loggerhead to actually stop logging during its occurrence.

  There may be actually two other situations that cause loggerhead to stop responding, that would be separate bugs from this one:

  1) Possibly a threading issue with loggerhead's use of the lru_cache (which could also possibly be this bug, although I have no idea yet).

  2) Loggerhead getting overloaded because it can't handle the load of codebrowse.