User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20060910 SeaMonkey/1.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20060910 SeaMonkey/1.0.5 Seamonkey 1.0.5 crashed on me. I had very many tabs open and was closing several tabs in succession, one at a time. Seamonkey crashed just after I closed a tab with a YouTube video. I got the following standard Windows error dialog: seamonkey.exe - Application Error : The instruction at "0x696355eb" referenced memory at "0x0000007c". The memory could not be "read". I have the inspector IIXII crash logger (<http://www.opera.com/support/search/supsearch.dml?index=432>) installed but unfortunately it could not log the crash, it complained about a timeout. The memory load on the computer was very high and I was already on swap so perhaps releasing the resources took too long and IIXII got bored waiting for the crash to happen, thus failing to log the crash. Reproducible: Didn't try Steps to Reproduce: n/a Actual Results: n/a Expected Results: n/a
How would the Inspector IIXII crash reporter from Opera help here? Normally SeaMonkey includes Talkback, but for various reasons the release builds don't. Talkback is currently the only way to get useful stacks since it has the application symbols on a server which can link the addresses to the functions/line numbers.
(In reply to comment #1) > How would the Inspector IIXII crash reporter from Opera help here? Normally > SeaMonkey includes Talkback, but for various reasons the release builds don't. > Talkback is currently the only way to get useful stacks since it has the > application symbols on a server which can link the addresses to the > functions/line numbers. IIXII is not a centralized system like Talkback and is in that way not tied to Opera at all. It is just a crash handler/logger program that creates a crash log file with register and stack contents, etc. I would have attached that crash log file to this bug report as extra info. I'd assume that having the info available would be better than not having it at all.
Stack contents would be almost useless, since there would be no function info. Ok, you could maybe guess what other stack it matches based on the file names, but that's all.
Sebastian: Did you ever experience this bug again with a current version of SeaMonkey?
Close this as "incomplete" for now, because there was no information how to reproduce this Crash, and also no Crash-Stack provided. Sebastian, if you can reproduce the crash using the current SeaMonkey 1.1.9 Release and/or the current Nightly-Builds, feel free to reopen and please submit actual information.