Closed Bug 266291 Opened 20 years ago Closed 19 years ago

Talkback broken in nightly trunk builds [was: Error message ??1nsCOMPtr_base@@QAE@XZ after installation (entry point, xpcom.dll)]

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.8beta1

People

(Reporter: bugzilla, Assigned: chase)

References

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041025 Firefox/0.9.1+
Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2004-10-27-06-trunk/

After installation of this build (using the stub installer) the error dialog
appears on startup.

Mozilla.exe - entry point not found. the proceedure entry point

??1nsCOMPtr_base@@QAE@XZ 

could not be located in the dynamic link library xpcom.dll

Clearing the error message does allow the browser to run successfully.

Reproducible: Always
Steps to Reproduce:
1.
Keywords: regression
Summary: Error message during installation → Error message after installation (entry point, xpcom.dll)
Same problem in WinXP Pro Corporate w/SP1 & Sp2 installed
-> me
Assignee: general → darin
Severity: normal → major
Target Milestone: --- → mozilla1.8beta
Yes, it seems to be something wrong with the xpcom.dll this days in the
Seamonkey-Trunk too. Since the SM-Nightly-Build 2004102507 I can't run the
calendar-extension [20041008-xxcal]. 

After installing the *.xpi, then restarting Mozilla the (german) Error-Message: 

Der Prozedureinsprungspunkt
"?InsertObjectAt@nsCOMArray_bas@@IAEHPAVnslSupports@@H@Z" wurde in der DLL
"xpcom.dll" nicht gefunden. 

occours. All the tricks from Bug 134432 won't help. I add this here before file
an Duplicate, but would file a new one if this is not caused by this bug here. 
> Since the SM-Nightly-Build 2004102507 I can't run the
> calendar-extension [20041008-xxcal]. 

the calendar extension needs to be rebuilt.  it was an intended outcome of this
change that components using the non-frozen, private mozilla APIs would be affected.
The problem is coming from the talkback component library (qfaservices.dll):

xpcom.dll
              1000204C Import Address Table
              10002468 Import Name Table
                     0 time date stamp
                     0 Index of first forwarder reference

                  93  ??1nsCOMPtr_base@@QAE@XZ
                 12D  ??_7nsGetServiceByContractID@@6B@
                 384  ?NS_NewGenericModule2@@YAIPAUnsModuleInfo@@PAPAVnsIModule@@@Z
                 5B4 
?assign_from_qi@nsCOMPtr_base@@QAEXVnsQueryInterface@@ABUnsID@@@Z
                 5B3 
?assign_from_helper@nsCOMPtr_base@@QAEXABVnsCOMPtr_helper@@ABUnsID@@@Z

It seems that it needs to be rebuilt before it will work correctly.  I was not
aware of the fact that it is not rebuilt with each release posted to
ftp.mozilla.org :-(
Summary: Error message after installation (entry point, xpcom.dll) → Talkback broken in nightly trunk builds [was: Error message after installation (entry point, xpcom.dll)]
Status: NEW → ASSIGNED
it appears that beast is running an old version of the tinderbox scripts which
does not delete the mozilla directory before a release build so qfaservices.dll
is not being rebuilt.

There is an effort underway to upgrade all the tinderbox scripts on all the
tinderboxen, or at least all the release build tinderboxen, but firefox has been
slowing that effort down.
Assignee: darin → cmp
Status: ASSIGNED → NEW
QA Contact: general → darin
I have gone back to:

http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2004-10-25-07-trunk/
mozilla-win32-installer.exe

as the last GOOD installation.

misspoke - this is on creature, not beast.

spent some time hacking at this and no joy - ran into 
https://bugzilla.mozilla.org/show_bug.cgi?id=243616
and had to return to the old tinderbox scripts.
Seamonkey build 2004102805 on WinNT4
1. IMO the string "??1nsCOMPtr_base@@QAE@XZ" should be included in the summary
to find it easier.
2. I get this error only one time at the end of the installation and every time
I do about:plugins or javascript:navigator.plugins.refresh(true);void(0);.
per comment 9, adding string to summary
Summary: Talkback broken in nightly trunk builds [was: Error message after installation (entry point, xpcom.dll)] → Talkback broken in nightly trunk builds [was: Error message ??1nsCOMPtr_base@@QAE@XZ after installation (entry point, xpcom.dll)]
*** Bug 266841 has been marked as a duplicate of this bug. ***
*** Bug 266826 has been marked as a duplicate of this bug. ***
*** Bug 267086 has been marked as a duplicate of this bug. ***
*** Bug 267182 has been marked as a duplicate of this bug. ***
*** Bug 267181 has been marked as a duplicate of this bug. ***
The error doesn't occur only while installation, but at other occasions too, e.g:
www.ebay.de, than "Einloggen" or "Mein ebay", than "Startseite" and choose any
category and click at any article, than "Diesen Artikel in mein ebay
beobachten": The error message appears. But it seems, there are no consequences. 
Not sure if this is on topic:
Mozilla is my default Browser. When I click on a link in MS Outlook the first time
it comes up right, but when I click a different link in MS Outlook the welcome
to Mozilla page comes up.
(In reply to comment #17)
> Not sure if this is on topic:

It's not.  What you describe has absolutely no resemblence to the problem this
bug documents.
put temporary hack into existing tinderbox scripts on creature to nuke the
fullsoft directory before checking it out.  tomorrow's release builds should fix
this problem - someone please confirm with tomorrow's bits and comment in the bug.

leaving bug open as a reminder to update the tinderbox scripts on creature.
Downloaded new build (11/02) and installed on PC w/ Win XP Pro SP1.  Error is
gone.   Thanks!!!

Did not test in other scenarios listed.
the error I once got when installing Mozilla

i.e.    "??1nsCOMPtr_base@@QAE@XZ"

is now gone with Build ID: 2004110305
Product: Browser → Seamonkey
resolving fixed based on comment 19, comment 20, comment 21 and own experience
on current nightlies.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Verified FIXED; no problem here with Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.9a1) Gecko/20050821 Mozilla/1.0
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.