User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.12pre) Gecko/20080116 Camino/1.6b1pre (like Firefox/2.0.0.12pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.12pre) Gecko/20080116 Camino/1.6b1pre (like Firefox/2.0.0.12pre) Something on the Tumblr.com dashboard is crashing Camino. Sign in, go to add new content and Camino bombs out. Reproducible: Always Steps to Reproduce: 1. Visit tumblr.com. Sign in. 2. Click one of the icons to add new content (e.g. Text or Quote). 3. Wait for the page to load... Actual Results: Camino crashes out. Expected Results: Render the page without crashing. I suspect this has to do with javascript -- either the script itself or something it loads. Follow the steps with javascript disabled and the pages work fine (albeit without the WYSIWYG editor). As far as I can tell, the crashing pages use a variant of the TinyMCE editor. Tumblr requires a login. I could create a test account if it would help?

Can you attach the crash log? http://caminobrowser.org/documentation/bugzilla/#crash

Sorry, here it is.

Is this reproducible without the various InputManagers and SIMBL plugins you are running? In the future, please get crash logs from non-hacked instances of Camino.

Sorry about that. This time I've removed some input managers (I don't think I have any other hacks installed) and used the Troubleshoot Camino app.

(In reply to comment #4) > Created an attachment (id=297575) [details] > Crash log #2 (without inputmanagers) > > Sorry about that. This time I've removed some input managers (I don't think I > have any other hacks installed) Apparently you didn't remove them all, as both SIMBL and 1passwd are still showing up in your crash log. Wanna try that again? :)

GAH! I had no idea SIMBL was even on here. Here's another log, hopefully with all the hacks removed :)

This is most likely the bug that we picked up for b2. Please try updating (through "Check For Updates") to 1.6b2, and retest.

Huzzah! That no longer crashes :)

My understanding is that we believe that makes this a dup of bug 279505 then (someone please fix the duping if I'm mistaken).

Yeah, that's where the patch is, and I don't feel the need to track it separately.