steps: 1. run mozilla -navigator 2. run process explorer http://www.sysinternals.com 3. select mozilla 4. scroll down to the file handles 5. right click each jar file handle, select close handle, and click ok 6. in navigator try to load mailnews, composer, chatzilla, inspector, or anything else. Expected results: 1. the jar handler would find out that it has no file handle, 2. would try to reopen the file to get a handle which it would then process...) 3. whatever you tried to load just loads. Actual results (opt-profile build): you get a 0x0 window containing now content. Reason: the jar handler found out that it couldn't read from the jar and returned a 0 byte file.

I went to the doctor and told him "it hurts when I bang my head on the desk". he told me to stop. now I am better.... We leave jar files open. Is that the bug your are telling me about? Or is it that we don't recover nicely when you poke your tools in mozilla? The former is a WONTFIX bug. we leave 'em open for performance reasons. The later is INVALID. See my doctor comment. Take your pick. :-)

Jar files are closed, when they are released and flushed from the jar-cache eventually: allready fixed. / WONTFIX... As for closing filehandles using a system tools: INVALID Recommend to close this one as WONTFIX.

VERIFIED