Closed
Bug 283358
Opened 20 years ago
Closed 20 years ago
Installing an extension then closing/opening Firefox causes an XPCOM error message box to appear twice
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: lists, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050223 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050223 Firefox/1.0+ Installing an extension then closing and re-opening Firefox causes the following error dialogue to appear twice: Title: XPCOM:EventReciever: firefox.exe - Entry Point Not Found Message: The procedure entry point ?Free@nsMemory@@SAXPAX@Z could not be located in the dynamic link library xpcom.dll After closing the box twice, Firefox appears to function normally. Reproducible: Always Steps to Reproduce: 1. Install an extension. I've been using u.m.o 2. Close Firefox. 3. Re-open Firefox. Actual Results: The above dialog box Expected Results: The procedure to succeed, or no box. Latest trunk build as of 2005-02-23.
Comment 1•20 years ago
|
||
All extensions or a special one ? This bug report looks invalid (extension which is using unfrozen interfaces is used)
| Reporter | ||
Comment 2•20 years ago
|
||
Several attempted from u.m.o - doesn't seem to be specific to one extension. This is on a clean profile too.
Comment 3•20 years ago
|
||
could be bug 282858
| Reporter | ||
Comment 4•20 years ago
|
||
Could be related, although they were throwing JS errors, and this was a physical dialogue box before getting the main browser window.
| Reporter | ||
Comment 5•20 years ago
|
||
Another thing to note: it only happens the first time it's reloaded with the extension install, which seems to suggest there's something wrong in the install mechanism itself. That does point to a possible follow-up issue to bug 282858.
Comment 6•20 years ago
|
||
Which extensions, in particular, are involved? This sounds like a typical error where extensions built against an older version of XPCOM are used with the newer xpcom_core and NS_Alloc functions.
| Reporter | ||
Comment 7•20 years ago
|
||
Looks like you're right. Newer builds of extensions don't seem to have the issue. Sorry, should have spotted that.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•