Closed
Bug 257296
Opened 20 years ago
Closed 19 years ago
javascript pop-up crashes browser.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: techadmin, Assigned: bugzilla)
References
()
Details
(Keywords: crash, Whiteboard: See comment 12)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 When I click on a javscript popup. eg. "Customer has root/admin access." The browser crashes with a 'program error' & tells me the application will now close. Where is the error log for firefox located? Thank you Reproducible: Always Steps to Reproduce: 1. go to http://www.servermatrix.com/managed_services.html 2. click on a link with a javascript pop-up (eg. "Customer has root/admin access.") Actual Results: Browser crashed with an "application error" Expected Results: Placed the pop-up in a new window. This seems to be a bug with extension support and http://ackroyd.de/googlepreview/ GooglePreview 0.3. I feel that a full application crash from any extension is a major issue.
Comment 1•20 years ago
|
||
If you're saying that you only crash with the extension enabled, then this bug is invalid. Crashes caused by an extension get reported to the extension author. Please clarify and/or test without the extension enabled.
The bug does not occur without the extension enabled. The reason I considered it a bug is because I think a full application crash means that there is a problem with exception handling by the main firefox application. In any case - I thank you for your time.
Comment 3•20 years ago
|
||
-> Invalid
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
gavin: erp. when did you start writing gecko policy? reporter: please see if you can get talkback working. crashes in gecko are problems that we want to shake out. perhaps #mozillazine can walk you through the process of using talkback.
Comment 5•20 years ago
|
||
I'm sorry if my resolution was wrong. I should have looked into more than I did, but I had been sifting through a large number of UNCONFIRMED bugs and jumped the gun a bit on this one. But by all means, if you feel it should be different, then change it. I certainly don't claim to be the writer of "gecko policy", nor do my conclusions have any more importance than anyone elses. Anyways, to get back to the bug, I've notified the author of "GooglePreview 0.3". Getting a talkback ID of this would be very helpful as timeless suggested. John, you may have already done this, but confirming that the extension is the culprit by either uninstalling it or using a new profile and trying to replicate the problem would also help. Also, you can try using safe mode (run firefox with the "-safe-mode" parameter). And of course, if you have since found any more information about the crash please post it here.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
I will probably enable talkback when i get the chance - not sure exactly how. Disabling the 'GooglePreview' extension was enough to stop it from crashing. Thats why I can be 99% sure the extension is the blame. I had almost completed my initial bug report - when I remembered to try disabling extensions to confirm the bug.
Comment 7•20 years ago
|
||
(In reply to comment #6) > I will probably enable talkback when i get the chance - not sure exactly how. Go to you Firefox directory and run talkback.exe in components subdirectory. In Settings menu Turn Agent On. But it should be enabled by default.
Keywords: crash
Comment 8•20 years ago
|
||
WORKSFORME. This could be a dupe of bug 198254, 0.9.3 does not have this fix, please retest with a nighlty branch build: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9/
Comment 9•20 years ago
|
||
I am the author of 'GooglePreview'. I cannot reproduce in 0.9.3 or in nightly Firefox builds, maybe this is an incompatibility with another extension. Could you please check if other extensions are enabled and if you still have the problem with GooglePreview 0.5: http://ackroyd.de/googlepreview/googlepreview-0.5.xpi Thanks
Comment 10•20 years ago
|
||
Another user sent a different link and I could reproduce this bug on my side. I was trying to set an attribute of one of the statusbar's child nodes, although the statusbar of that particular window was hidden. Bad code on my side, but Firefox/Mozilla should not crash on that. This version of the extension has my fix (I think :-)) http://ackroyd.de/googlepreview/googlepreview-0.6.xpi
Comment 11•20 years ago
|
||
I'm getting this pretty frequently. XP SP2 FF1.0PR It doesnt happen always but it does happen ONLY with javascript pop-up boxes. Worth1000 view full images, voting on cnn.com, etc. Usually I have a lot of tabs open when this happens, but this may be a coincidence. I have sent a talkback about 4 times so you guys should be able to see whatever other data you need.
Comment 12•20 years ago
|
||
(In reply to comment #11) > I'm getting this pretty frequently. XP SP2 FF1.0PR > > It doesnt happen always but it does happen ONLY with javascript pop-up boxes. > Worth1000 view full images, voting on cnn.com, etc. > > Usually I have a lot of tabs open when this happens, but this may be a > coincidence. I have sent a talkback about 4 times so you guys should be able to > see whatever other data you need. This bug was reported before 1.0PR and is caused by an extension. General pop-up problems with 1.0PR are bug 255372, not this one.
Updated•20 years ago
|
Whiteboard: See comment 12
Comment 13•19 years ago
|
||
(In reply to comment #12) > This bug was reported before 1.0PR and is caused by an extension. So it should be resolved as invalid. Without any TB data this report is useless and seems fixed in the meantime. Feel free to reopen if you can reproduce the problem with current builds and without extensions.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 19 years ago
Resolution: --- → INVALID
Comment 14•19 years ago
|
||
user245@hotmail.com: you may have sent talkback reports, but there's no way we're going to randomly figure out they're yours. how about running the talkback application and copying their incident ids somewhere?
You need to log in
before you can comment on or make changes to this bug.
Description
•