User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:220.127.116.11) Gecko/20060613 Camino/1.0.2 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:18.104.22.168) Gecko/20060613 Camino/1.0.2 using the portion of the website that allows you to view vehicles/change colors, etc causes irretrievable hang. some hotspots dont activate pointers. Reproducible: Always
With Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060908 BonEcho/2.0b2 it only uses 100% of cpu during the page loads. I believe you mean following URL? http://www.jeep.com/en/wranglers/360/wrangler/exterior/index.html?tname=wrangler360 This page contains a java applet. Which version of java do you have installed? If you don't have the latest version 1_5_0_08 try to update and test again.
Please look at bug 256763 because your one could be a dupe of that bug.
Henrik, this is a Camino bug, please triage using Camino unless it's apparent that this bug is cross-platform.
(In reply to comment #3) > Henrik, this is a Camino bug, please triage using Camino unless it's apparent > that this bug is cross-platform. That's why I ask and give hints. Without testing we aren't able find out if it's cross-platform related.
Java bugs on Mac OS X are almost never cross-platform, given the platform-specific nature of Apple's Java libraries and the way Mozilla talks to Java (JEP). Reporter, please be specific about which page on the site is causing problems. Most of the site if Flash-based ("hotspots") and seems to work fine, but the URL mentioned in comment 1 does have an applet and does crash a recent Cm 18branch on 10.3.9. (In Safari, the applet basically doesn't load; I can occasionally get something to display by clicking the "right" combination of buttons, but otherwise it's just a blank white box, and it spews tons of errors in the console.) That tends to make me think the applet is broken, but we shouldn't crash ;)
Actually, I was a little hasty to confirm. I don't crash in Cm 102 or 103rc2, nor in Firefox 1506. I don't crash in this morning's official branch nightly (so the crash might have been related to it being a debug build). The applet works fine in all those cases; it's just dog-slow.
(In reply to comment #6) I suspect this crash is unrelated to this bug. I've just been digging around in bmo, and found that there's a small class of crash logs which, like this one, have (on the main thread) the two lines LookupClass and IsInstanceOf at the top of the stack and JEPCreateJavaApplet somewhere below it (in the same stack): bug 330005 comment 1 (attachment 214651 [details]) bug 332706 comment 9 (attachment 217253 [details]) bug 338850 comment 2 (attachment 222898 [details]) I don't believe I've ever seen one of these myself, and I don't know what to make of them. But it's worth keeping an eye on them. At some point, in the very distant future, it may be possible to figure them out :-)
jhasson, is this still a problem with Camino 1.5 and/or a new Java Embedding Plugin?
Closing INCO. If anyone can reproduce this with a recent build of Camino, feel free to reopen.