Closed Bug 100441 Opened 23 years ago Closed 23 years ago

"Unable to enumerator app shell components" every time on startup

Categories

(SeaMonkey :: UI Design, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 76339

People

(Reporter: sfraser_bugs, Assigned: law)

Details

(Keywords: qawanted)

The Mac OS X build gives this error every time on startup:

Unable to enumerator app shell components, GetSubtree rv=0x80510003

which comes from here:

http://lxr.mozilla.org/seamonkey/source/xpfe/appshell/src/nsAppShellService.cpp#366

What does this indicate is broken?
Is this appshell component stuff obsolete? Can we remove it? The only client that 
I can find in the tree is in extensions/access-builtin.
I don't see this error starting up Fizzilla/2001091313 (0.9.4), at least not on the Console. 
Rather, I see "CFM failed to set the stack limit because requested limit is lower than current."

Thus, it would seem this bug is no longer valid, and should be marked WFM.
you need a debug build to see these errors. they go to the sioux console, not the 
osx console. i'm pretty sure this isn't WFM.
I see this every day in my current debug builds, and it also happens on Mac 
classic builds, and on other platforms.
OS: MacOS X → All
Hardware: Macintosh → All
can we at least fix the grammar in the assert? ;)
yes, nsIAppShellComponent stuff is obsolete, in favor of nsIAppStartupNotifier.
I'm working in bug http://bugzilla.mozilla.org/show_bug.cgi?id=76339 to get rid
of it. 

*** This bug has been marked as a duplicate of 76339 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.