Closed Bug 145407 Opened 23 years ago Closed 23 years ago

Error on startup: Entry point not found: ?AppendFromReadable@nsAString@@IAEXABV1@@Z in xpcom.dll

Categories

(SeaMonkey :: Installer, defect)

Product:
SeaMonkey
Component:
Installer
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: superbiskit, Assigned: dveditz)

References

Details

Behavior is very similar to Bug#14138. Build 2002-05-16-08 (from LATEST link), ditto 2002-05-17-04 (also LATEST) Win2000pro on first launch after Uninstall&&install XPCOM:EventReceiver:Mozilla.exe Entry point ?AppendFromReadable@nsAString@@IAEXABV1@@Z in xpcom.dll Warning dialog comes up twice during program loading. There's a *lot* of strange behavior in this build, I can't tell whether it's related. One effect is that I cannot call up about:mozilla to get the version string. (I get a blank browser page with a blank address control, in fact the address control is usually blank).
Did you install spell ckecker? I faced the same problem. It is not a problem that I installed new build over an old build without uninstalled. After investigation, I found that the problem should be from the spell checker.
*** Bug 145319 has been marked as a duplicate of this bug. ***
*** Bug 145457 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
My (Windows NT 5.1; en-US; rv:1.0rc3) Gecko/20020518(06) from the /latest-1.0.0/ folder does the same, and has been for several past nightlies. Occurs twice, but only on the first running of a new install. The only components I have installed are MozGest, UABar, Calendar (All of which work fine), and Spellchecker (Which doesn't work at all). Seems to be Spellchecker related.
Invalid. This bug is caused by installing the spellchecker from mozdev.org fx http://spellchecker.mozdev.org/download/w32spellchecker20020513.xpi this xpi file installs to dll files in the componenets directory: components\myspell.dll components\spellchecker.dll these two files are the cause of this bug! Removing those two files removes the xpcom entry point error...
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
FYI: uninstalling mozilla from Control Panel and then reinstall Mozilla will still produce the entry point error since removing mozilla doesn't remove add on products. So the safe way to reinstall/upgrade mozilla is to do a *complete* wipe of your mozilla.org directory and the install Mozilla again...
. . . and /that/ situation is a bug! Install-over is really important for users. But, probably, not this one.
The decision not to remove things we didn't install was a conscious one. Yes, it may cause problems in some situations, but it saves users from some inconveniences and some truly awful problems. (See bug 69153 for what can happen; Linux does something like you've requested.)
Responding to Comment#8. The bug I'm thinking of is the universe of problems related to "Install-over-existing-installation." There are, indeed, good reasons for leaving add-on's around. I'm quite torqued up that I need to keep re-installing add-on's whenever I update; that's at least once a week. In an ideal world, it should be possible to isolate Mozilla from broken plug-ins; or cause the error message to identify the plug-in, rather than a Mozilla component.
In an ideal world components authors would restrict themselves to using "frozen" interfaces, and there would be enough such interfaces to support what they're trying to do.
Re. #10: Sigh! I know. And I imagine MozDev have their fingers fairly close to the pulse! I hate to think what more arms-length developers do. Of course, a release called "1.0" is a *real* good time for freezing the API. Or, at least, bringing it into the kind of configuration control where it only changes if something is totally broken.
There have been some major changes recently to the nsAString family in an attempt to freeze them for 1.0 so this current pain may be inflicted in an attempt to prevent future pain. I've also heard that developers are encouraged to link in a copy of the string library rather than attempt to use the copy provided by the xpcom library. That way they are protected from such changes.
*** Bug 146186 has been marked as a duplicate of this bug. ***
verified
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → gbush
*** Bug 147074 has been marked as a duplicate of this bug. ***
I also have this bag... Beginning from the build RC2... (Interesting points this happens on my computer at the office and doesn't on my home computer) May be some additional symptom that in this case mozilla does not change the address in the tab...
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
If you have the problem talked about in this bug then remove the spellchecker or upgrade to a version compatible with the version of Mozilla you have. If you have a problem that's merely similar then open a new bug. reclosing.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
*** Bug 151980 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.