Closed Bug 324252 Opened 19 years ago Closed 16 years ago

Multiple "Failed to load XPCOM component" messages, when (re)building <compreg.dat>

Categories

(SeaMonkey :: Build Config, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: eyalroz1, Unassigned)

References

Details

Attachments

(1 file)

In recent sm trunk nightlies (specifically, 2006-10-06), on startup, my Javascript console shows the following:

Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\myspell\en-US.aff
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\myspell\en-US.dic
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\fullsoft.dll
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\talkback.cnt
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\talkback.exe
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\talkback-l10n.ini
Failed to load XPCOM component: E:\Program Files\mozilla.org\SeaMonkey\components\BrandRes.dll

and so on and so forth (if the full list is important let me know). sm's functionality seems fine otherwise (e.g. spelling works). Highly annoying.
This happens because those files are in the components directory, but aren't XPCOM components. When did this start happening? I can't see any recent changes that should have affected this (assuming you meant 2006-01-06 and not 2006-10-06).
*** Bug 330894 has been marked as a duplicate of this bug. ***
I've resummarized.

"If a file in a newly-downloaded build is missing or corrupted, file the bug in this component."

-> Component: Build Config
Component: General → Build Config
Summary: javascript console messages: "Failed to load component: X" → Javascript console reports failures to load several XPCOM components
Summary: Javascript console reports failures to load several XPCOM components → Error Console reports failures to load several XPCOM components
I'm sure this is a minor issue, but it just gets on my nerves when debugging...
Keywords: helpwanted
I have MailNews loading on startup btw, this may not happen when only the browser loads. Also, it does not happen at all with a clean profile.
Blocks: 343838
This should be fixed in trunk/1.8branch builds with the patch from bug 216382. And it is a dup of some older bug, IIRC.
Depends on: 216382
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070112 SeaMonkey/1.5a] (nightly) (W2Ksp4)

Bug still there, "missing Talkback components" while these files are there,
unpacked from Zip file, with legacy profile:
{
Failed to load XPCOM component: D:\Progs\seamonkey\components\BrandRes.dll
Failed to load XPCOM component: D:\Progs\seamonkey\components\fullsoft.dll
Failed to load XPCOM component: D:\Progs\seamonkey\components\master.ini
Failed to load XPCOM component: D:\Progs\seamonkey\components\talkback-l10n.ini
Failed to load XPCOM component: D:\Progs\seamonkey\components\talkback.cnt
Failed to load XPCOM component: D:\Progs\seamonkey\components\talkback.exe
Failed to load XPCOM component: D:\Progs\seamonkey\components\talkback.hlp
}
SM started with "-browser -jsconsole".

It seems to happen on the first run only of a new nighly.

(See bug 339139 for Thunderbird)
Assignee: general → nobody
Blocks: 339139
QA Contact: general → build-config
Summary: Error Console reports failures to load several XPCOM components → Multiple "Failed to load XPCOM component" messages on (1st) startup
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a4pre) Gecko/20070426 SeaMonkey/1.5a] (nightly) (W2Ksp4)
[Mozilla Thunderbird, version 3.0a1 (20070427)] (nightly) (W2Ksp4)

(In reply to comment #8)
> It seems to happen on the first run only of a new nighly.

Actually, it happens each time <compreg.dat> is (re)built:
*SM file is in <\components> application directory
*TB file is in each profile directory

(You can (safely) trigger it by manually deleting the file.)
No longer blocks: 343838
Summary: Multiple "Failed to load XPCOM component" messages on (1st) startup → Multiple "Failed to load XPCOM component" messages, when (re)building <compreg.dat>
(In reply to comment #1)
> When did this start happening?

Regression timeframe:
[Mozilla Thunderbird, version 1.6a1 (20051213)] (2005-12-13-10-trunk) (W2Ksp4)
[Mozilla Thunderbird, version 1.6a1 (20051214)] (2005-12-14-08-trunk) (W2Ksp4)
<http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=ThunderbirdTinderbox&branch=HEAD&branchtype=match&sortby=Date&hours=2&date=explicit&mindate=2005-12-13+10&maxdate=2005-12-14+09&cvsroot=%2Fcvsroot>
Maybe bug 320148 ?
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a6pre) Gecko/2007060902 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

Location changed after
{{
2007-06-07 11:41	mcsmurf%mcsmurf.de 	mozilla/suite/installer/windows/packages 	1.6 	11/9  	Talkback is now an extension in SeaMonkey
}}

New messages are
{{
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\BrandRes.dll
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\fullsoft.dll
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\master.ini
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\talkback-l10n.ini
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\talkback.cnt
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\talkback.exe
Failed to load XPCOM component: D:\Progs\__Mozilla-SR\seamonkey\extensions\talkback@mozilla.org\components\talkback.hlp
}}
No longer blocks: 339139
I don't remember when SM & TB stopped using Talkback on 1.9 Trunk;
but that (part too) is WorksForMe now.
Status: NEW → RESOLVED
Closed: 16 years ago
Keywords: helpwanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: