click on any child member of a context menu and browser crashes and must be terminated using end task

RESOLVED INCOMPLETE

Status

()

Firefox
Menus
--
critical
RESOLVED INCOMPLETE
11 years ago
9 years ago

People

(Reporter: GµårÐïåñ, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 2009-04-08)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Starting with the 2.0.0.7 update release, every single time you right click on the webpage content (ANY WEBSITE OR PAGE CONTENT) and click on a main menu items, you are fine. If you put your mouse over ANY child menu, it immediately pops us with the error:

[Exception..."Component returned failure code: 0x8000fff (NS_ERROR_UNEXPECTED)
[nsIDOMXULDocument_MOZILLA_1_8_BRANCH.popupRangeParent]" nsresult: "0x8000ffff
(NS_ERROR_UNEXPECTED)"location:"JSframe::chrome://browser/content/browser.js::
anonymous::line 3932" data: no]

I have the screen shot as well. This will freeze the application and nothing more can be done in any shape or form and when you close the application, it remains in memory and has to be killed using terminate process tree. I have disabled all extensions, still does it. I have started in safe mode and it still does that. I am at my wits end with this.

Reproducible: Always

Steps to Reproduce:
1. Open browser
2. Go to any website or nothing
3. right click anywhere
4. browse to a submenu on the context menu
5. BAM!
Actual Results:  
Exactly what I said in the summary "or not so summary with all the details" :D

Expected Results:  
It should open up the item and allow you to click on the action but nothing is available and crashes every time. I hate IE and I have been reduced to using it because its the only option.

I have uninstalled COMPLETELY and reinstalled and still does this. I have years of bookmarks, extension settings, custom whitelists, blocklists, so on and this is going to suck if I have to redo it all over again. I am using the default firefox theme, nothing fancy here.

I am running Vista Ultimate x64 on an AMD Turion 64 x2 using an HP tx1000 laptop. I have 1 GB of RAM and over 250 GB hard disk. I wish we could upload screenshots.
If this happened to me (and not to anyone else) I'd immediately suspect extensions. And if it's not an extension or theme, it could be a plugin, profile problem or an unclean installation.
See http://kb.mozillazine.org/Firefox_crashes
http://kb.mozillazine.org/Talkback
(Reporter)

Comment 2

11 years ago
Thank you for your input ria but as I stated in detail, I have tried it with many different configurations, including with and without extensions, safe mode, completely clean uninstall and reinstall. It simply has occured since 2.0.0.7. I have been using firefox since before they were a twinkle in the browser competition market. I am also a developer with senior level experience for 10+ years. I don't submit bugs lightly or without feeling compelled, I am just not familiar enough with firefox source to mess with it and I don't have the time to spend to learn it while I can't use it. Anything else you think might be the cause?
Over what sub menu item did you exactly hover with a crash as result?
(Reporter)

Comment 4

11 years ago
As stated in detail, ANY sub menu. For instance when you load a webpage that has a frame (and before you ask which website, ANY website doesn't matter) and you right click on a specific frame and you go to the submenu where you choose to show only that frame and it crashes as soon as it paints the submenu. If there are extensions installed and not in pure firefox mode, then any other many submenus there will achieve the same, regardless of which extension it is. I have traced it to the core code inside the browser.js file that is in the chrome folder as part of the jar file but as stated before, I know what its doing in pseudo concept but not in context of the firefox source code.
This Frame -> Show Only This Frame WFM with latest branch and trunk builds on Windows XP.
(Reporter)

Comment 6

11 years ago
unfortunately that doesn't help me because I am not running XP, I am on a Vista Ultimate 64 bit machine. and This Frame -> Show Only This Frame -> crash
Without at least a Talkback ID (comment 1) no one can do much about it.
(Reporter)

Comment 8

11 years ago
Firefox does not generate a TalkbackID for this matter. Each time the program crashes, I have checked the Talkback agent and there is nothing listed there. I have the screenshot for the error but nowhere to post it.
(In reply to comment #8)
> Firefox does not generate a TalkbackID for this matter. Each time the program
> crashes, I have checked the Talkback agent and there is nothing listed there. I
> have the screenshot for the error but nowhere to post it.

http://www.imageshack.us
(Reporter)

Comment 10

11 years ago
Thank you stephen, I am aware of the services where I can host an image but I don't want to create accounts that I don't need just to share a screenshot for a problem I hope will be solved and I will hopefully not have again. I am not a Microsoft fan but one thing to be said about them, even its patchware, they at least patch and fix problems often as they get them. With open source, its a **** shoot and that's why it will never become mainstream.

Comment 11

9 years ago
can you reproduce this unconfirmed problem using newest firefox 3.x or 3.1 beta?
 http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: CLOSEME 2009-04-08
@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available. Some helpful information you can provide us is found at http://quality.mozilla.org/bug-writing-guidelines. You should also use a recent version of Firefox, from http://www.getfirefox.com.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.