Presuming this is reproducible, you should enter this state, then take
thread dumps (via ctrl-break, ctrl-\, jconsole, jstack, jvisualvm,
etc).
If you want more info on what's happening with gc, use -verbose:gc and/
or -XX:+PrintGCDetails
If you want another level of analysis, use a performance p
On Fri, Apr 15, 2011 at 4:17 AM, Alan wrote:
> Holy cow wall of text. I really couldn't get through the whole thing,
> but I scanned it and I don't see you mentioning output-stream
> buffering, which would be one of my primary suspects for this sort of
> behavior.
I didn't mention it because it i
Holy cow wall of text. I really couldn't get through the whole thing,
but I scanned it and I don't see you mentioning output-stream
buffering, which would be one of my primary suspects for this sort of
behavior. Sorry if you've already considered this. As for why it
allocated a bunch of heap: if yo
I've been using Clojure to automate some file management tasks over
here; in particular, I whipped together about 100 lines of code to
build and maintain a hash database of certain files and thereby
efficiently discover duplications among these files. (Basically, it
uses a subdirectory of the files
