Closed Bug 244679 Opened 22 years ago Closed 21 years ago

"Procedure Entry Point ??_7nsQueryInterface@@6B@ could not be located in the dll xpcom.dll" error on Mozilla (1.7rc2) launch

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: inspired, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 I had just downloaded and installed the Home Button (0.6), MNG Support (1.0.6-1 for Windows), and Google Bar (0.8) extensions, then closed Mozilla so they would reappear. , an error was issued stating the following: "The procedure entry point ??_7nsQueryInterface@@6B@ could not be located in the dynamic link library xpcom.dll" There were no noticeable adverse effects besides this error message. Upon subsequent launches, this error message did not occur. I took the initiative to test each extension individually, and I found that the Home Button produces the error on the next launch, and the MNG Support and Google Bar extensions produce the error when mozilla is closed.I tested the three in order as well as each individually, and they consistantly produce the error. Reproducible: Always Steps to Reproduce: 1. Download the Home Button 0.6 extension, install in application folder. 2. Download and install the MNG Support 1.0.6-1 for Windows extension. 3. Download the Google Bar 0.8 extension, install for all users. 4. Close Mozilla. 5. Launch Mozilla. Actual Results: An error message stating "The procedure entry point ??_7nsQueryInterface@@6B@ could not be located in the dynamic link library xpcom.dll" appears. Expected Results: Not give an error message ;-) Additional Notes: -Modern Theme -Using StyleXP 2.03 to skin Win XP with SlateDARK theme from themexp.org -Specs: Win XP Home SP1 2.66 GHz P4 Northwood B 512 MB PC 2700 DDR RAM Asylum GeForce 4 Ti4200se
Sounds like one of those extensions is relying on unfrozen APIs that have changed... Definitely not an XPCOM issue, and probably invalid.
Assignee: dougt → general
Component: XPCOM → Browser-General
QA Contact: general
This was the first bug i've ever run across. I just submitted it as XPCOM because the error showed xpcom.dll. Sorry.
This is a screenshot of the error dialog. I am running Windows 2000 on an AMD Athlon XP 2200 with 1GB of RAM. My Motherboard is a Shuttle AK32E, I have a GeForce FX 5200 128 MB Video Card, A Sound Blaster Audigy MP3 Sound Card.
I was experiencing this same bug, I installed Dependancy Walker but when I ran Firefox via it, it didn't produce this error. Now this error does not occur. I can attach my image if needed.
No response from reporter, old build. Please resolve this bug.
Product: Browser → Seamonkey
Please mark as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Version: Trunk → 1.7 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: