User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:22.214.171.124pre) Gecko/2008121820 Camino/2.0b1 (like Firefox/3.0.6pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:126.96.36.199pre) Gecko/2008121820 Camino/2.0b1 (like Firefox/3.0.6pre) Looked like it bogged down for a second there possibly due to a memory issue I usually run with several tabs open and Camino does fine but this is first instance I have ever seen it crash. I have a hunch it maybe a conflict with Growl. I usually run it in the background and it looked like Growl was in the process of displaying a notification when it happened but I haven't seen it have a problem before. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
email@example.com, if you start seeing this repeatedly, please do remove 0x1400000 - 0x1400ffc +com.growl.GrowlSafariLoader 1.0 (1.1) /Library/InputManagers/GrowlSafari/GrowlSafariLoader.bundle/Contents/MacOS/GrowlSafariLoader 0x1413000 - 0x1417ff3 +eu.willmore.GrowlCamino GrowlCamino v1.3beta2 (1.5beta) <3933f98c24b559e4cfcc799284c092f3> /Library/InputManagers/GrowlCamino/GrowlCamino.bundle/Contents/MacOS/GrowlCamino and see if the crash then goes away. It's certainly possible that the Growl InputManagers are at fault. > Application Specific Information: > objc: FREED(id): message isEqual: sent to freed object=0x13b78550 Stuart, any idea why we are starting to see these messages sent to freed objects (bug 470159 comment 11 mentions another one)? The "bogged down for a second there" description is also consistent with the slow response stuff mentioned in the other bug, too.
Closing INCO due to lack of updates. If you still see this problem in Camino 2.0b2 or a recent nightly and can supply the requested additional information, you may reopen this bug.