User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 My Firefox installation generall crashes once reaching approximately 1.4GB memory usage. This crash does not go through crash reporter, it immediately triggers the "there is a problem with this program" dialog in windows 7. I was able to solve this problem by setting image.mem.discardable = true image.mem.decodeondraw = true As far as i understand it this discards drawn images in background tabs and thus saves memory, preventing firefox from crashing. The problem with tabcandy is that it redraws all tabs to create the icons in the tab groups, which means that all images on all tabs get un-discarded, consuming memory and crashing firefox. Reproducible: Always Steps to Reproduce: 1. set image.mem.discardable = true and image.mem.decodeondraw = true 2. Open lots (100+) of image-heavy (many images or big images) tabs 3. open tabcandy and let it render the tab group 4. crash
reporter please provide crash report.
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report we're using memory mapping for the graphics card which reduces the amount of memory available for the rest of our work which is why we crash near 1.4gb instead of 2.0gb as we used to in previous versions.
While the underlying OOM/virtual address space issue still persists tab candy does not worsen it anymore due to changes in the session restore. (something about staged session restore *mumble mumble*) => marking it as resolved