Closed Bug 416036 Opened 14 years ago Closed 14 years ago
###!!! ASSERTION: Oops! You're asking for a weak reference to an object that doesn't support that
.: 'factory Ptr', file ns Weak Reference .cpp,
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4pre) Gecko/2008020621 Firefox/3.0b4pre Note, its the same assertion as in Bug 414808 but this is on different scenario Steps to reproduce: - New Firefox Profile - Install the Session Saver Extension (this make it easier to reproduce this problem, but its not necessary) https://addons.mozilla.org/en-US/firefox/addon/2324 - go to http://www.popuptest.com/popuptest12.html - the popup warning bar is displazed, choose "allow pop-ups for www.popuptest.com - Reload the Site - the 3 popup sites are displayed -Quit Firefox with this 3 pop up windows open Firefox does not close and instead you get a lot of error messages and a assertion: ###!!! ASSERTION: Oops! You're asking for a weak reference to an object that doesn't support that.: 'factoryPtr', file nsWeakReference.cpp, line 109
Note, the problem in general here is causing also bug 416048.
note: the same assertion comes also up when a extension is downloaded/installed with the Extension Manager.
Flags: blocking1.9? → blocking1.9+
Tomcat, can you get a stack for this assertion?
(In reply to comment #3) > Tomcat, can you get a stack for this assertion? > done :) this stack is from the case when i install a extension with the extension manager (like going to addons.mozilla.org , choose a extension and click on install now and on "install") with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008021917 Minefield/3.0b4pre
Bummer, the stack is all JS. This definitely looks like a bug in the extension. Would be excellent with a JS stack. Ping me on irc and I can help you create one.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
verified fixed using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4pre) Gecko/2008022101 Firefox/3.0b4pre thanks jonas !
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.