Closed Bug 73513 Opened 23 years ago Closed 23 years ago

Browser crashes on startup [@ xpcom.dll]

Categories

(Core :: Networking: Cache, defect)

Product:
Core
Component:
Networking: Cache
Platform:
x86
Windows ME
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: elst93, Assigned: gordon)

References

Details

(Keywords: crash, smoketest, topcrash, Whiteboard: [cache])

Crash Data

Attachments

(1 file)

guards disk cache hashtable from failed initialization
393 bytes, patch
Details | Diff | Splinter Review 
It's probably been said before, but still ;)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; 0.8.1) Gecko/20010306
BuildID:    20010326 installer (14:46, 7.7Mb)

Mozilla crashes on startup splash screen. Error message given by Windows is an
error occured in XPCOM.DLL

Reproducible: Always
Steps to Reproduce:
Just trying to open up Mozilla. Even after a reboot it wouldn't work.

Actual Results:  No go

Expected Results:  Go

I downloaded Moz 20010326 two times (a bitch on a V90 modem). One time to
install it and finding that error. The second time to insure it wasn't a wrong
file. Both were the installer (timestamp 14:46) of 7.7Mb

I'm back at the most reliable Mozilla out there.
Excuse me, timestamp was 14:22
Confirming. I get a crash on startup as well, using the afternoon respin bits
(pushed out between 2 and 3pm).

However, if I create a new profile (use the -profilemanager switch), then 
I can start up fine on that new profile. (Jorden: can you see if you can 
start on a new profile?)

With my old profile, I tried deleting 'Cache', but I still crashed (although
the top level 'Cache' folder would be recreated). 

A talkback report has this top of stack, although no function symbols. 

xpcom.dll + 0x3146a (0x60e3146a) 
xpcom.dll + 0x30b2b (0x60e30b2b) 
necko.dll + 0x859e (0x6073859e) 
gkcontent.dll + 0x45919 (0x01c65919) 
gkcontent.dll + 0x4eda2 (0x01c6eda2) 
gkcontent.dll + 0x4f284 (0x01c6f284) 
gkcontent.dll + 0x86951 (0x01ca6951) 
gkcontent.dll + 0x86d18 (0x01ca6d18) 
... snip ...

This will be a smoketest blocker tomorrow (can't start on existing profile), 
although I'm a little curious as to why more people aren't seeing this (this
was the only related report I could see in Bugzilla).
Assignee: asa → neeti
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking: Cache
Ever confirmed: true
Keywords: smoketest
QA Contact: doronr → gordon
I tried two other systems with this same build (both win98; my system win2k). 
On one system, I would crash on an existing profile. But on the other system,
I would not crash on an existing profile. Don't know why.
for me, mozilla 20010308XX (don't know what the version is exactly) crashes at 
startup on mac (os 9.1; en-US; nightly build as of a few minutes ago).  tried 
trashing the user profiles, tried rebooting.  it simply crashes every time with a 
type 2 error.  tried re-downloading/re-installing with the same problems.

this may not be the same problem that is causing the windows version to crash.  
if not, i can open a separate bug report.  i did not see one listed for ALL or 
MAC.

-->gordon
Assignee: neeti → gordon
I just tried the first build from 3/27/01 and had the same problem (crash on 
startup).  Can't even get past splash screen.
John --> I tried a new profile. No go either. It keeps crashing at the splash
screen, same error.
Sorry :-((
I just created a new profile and was able to launch the product. But I have a 
mozilla throbber instead of the NS throbber (installed commercial build).
Can we get a better stack crawl?

try specifying your profile at startup time with the -P option.
pavlov: this sounds very similar to the other splash screen startup crash from
last week when libpr0n was enabled.  has something perhaps changed that would
have invalidated that patch?
I did try the '-P foo' workaround for Friday's crash, but that didn't do the
trick in this case. 

Sorry, can't get a better stack trace, since there are no symbols for this 
build on the talkback server (or I think that's why). 

Oddly, my mozilla opt. tree, built last night starts cleanly with an existing
profile.
Are you sure it's related to the profile, and not to the page that loads at 
startup? Mine starts okay with a blank page, but then dies in NKCACHE.DLL 
(called from NECKO.DLL, called from GKLAYOUT.DLL) depending on what page I go to 
(and it isn't the same spot on the page each time).

Sorry I don't have more useful stack information, this is what I could get out 
of VC++.
so, has anyone found this using the mozilla .zip file? or just using installers?
Whiteboard: [cache]
With current builds (on win2k)

mozilla installer exe 3/27    -- existing profile (migrated) --  Starts OK
mozilla zip file 3/27         -- existing profile (migrated) --  Starts OK
my own mozilla build midnight -- existing profile (migrated) --  Starts OK
Netscape installer 3/27       -- existing profile (migrated) --  Crash
Netscape installer 3/27       -- new profile                 --  Starts OK

Is this a widespread issue, or related to some narrow subset of users?
Whiteboard: [cache]
alright, so we can safely say this is not blocking mozilla at all, then?
Well, it does affect some people on mozilla builds (at least with 2pm respin
03/26; there isn't a specific mention of a mozilla build 3/27 crashing, 
although perhaps that is implied in some earlier comments). What sez IRC:
are a lot of people experiencing this crash, or just people is some specific
initial (profile) state.
... but no, it's probably not a blocker, since the workaround is to create 
a new profile (inconvenient, and not obvious, but ...)
Whiteboard: [cache]
*** Bug 73746 has been marked as a duplicate of this bug. ***
gordon:  r/sr=darin (for your 3/27 patch)
reducing to critical to get off the smoketest blockers list.
Severity: blocker → critical
I've downloaded and installed 20010328 (the Mozilla installer). On the normal
profile I had the XPCOM.DLL error. I started a new profile and it started okay.

Now, where in Mozilla can I add my present (old) profile (bookmarks, passwords
etc.) to a new version's new profile? I can't. Shock. What the heck was my
Bugzilla password? etc.
So an option for the future would be to set a directory for your bookmarks,
passwords etc, and be able to exchange that amongst profiles!

One thing for Win9x/ME versions that could get rid of a couple of stupid errors:
Tell the user to reboot after installation. As Windows does write somethings to
the registry and ini files (to??) reread these.

Jord, using Moz 0.9 to write to Bugzilla :))
Question: Can I by-pass the XPCOM.DLL and still start up with my own profile?
I can't exchange the profile folders, as I tried that :-((
Does this still occur?  I've checked in some fixes for the cache.  If we're still 
crashing, has the crash moved?

I didn't have a problem with today's build on win2k, starting with the same
profile that had me crashing yesterday. Looks good to me.
build 2001032804, WinME: 
still problems launching (after reboot) first netscape6.01, then (finished
netscape6.01) mozilla -> crash
problem disappears after launching (after reboot) first mozilla, then (finished
mozilla) netscape6.01, then (finished or not) mozilla: no crash, but cache-data
(pics, banners) are not displayed correct (black at all, black lines through pics)
Still a bug? 
Black lines through images is a known libpr0n problem.

Build ID Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; 0.8.1) (20010329)
I downloaded it and in a bout of testing wrote down my Bugzilla password, then 
removed all other instances of Mozilla I had on standby in WinME. Rebooted to be
sure to get rid of all remnants.
Installed Mozilla 0.8.1 that I downloaded today (20010329), installed it,
rebooted to make sure it was written to the registry.

Made connection to the internet, started up Profile Manager, deleted the old
second profile, made a new profile. Tested the old first profile, which would
still crash on the XPCOM.DLL
Rebooted, made new connection, started up the new profile. It works.

* Pictures loading show black bars over it.
* The "About Mozilla" page to get the build ID from, started up very strange,
with the Mozilla picture behind the text. Had to reload that one.
* The Flash plug in that was included in other versions seems to be missing
again, although it is a threat not seeing those flashy adverts on some pages ;-))
* Loading of pages is back to lightning speed! Good job there.
* I still miss an option to load the bookmarks from another profile. IE
bookmarks are imported automatically, so why not old profile bookmarks as well?

I will test it some more :-))

Okay, I'm marking this fixed.  The disk cache doesn't appear to be crashing on 
startup since the additional guards were checked in.

If it crashes on startup now, it's a different bug.

Thanks everyone.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Thanks gordon. (Note to Jorden: the image glitches are known problems; I'm 
not sure about the Flash issue, but it should pick up the plugin from a Nav4.x
directory (I think)); You can import bookmarks from any file with 'File->Import 
Bookmarks' from within the bookmark manager).
Status: RESOLVED → VERIFIED
adding crash, topcrash keywords and [@ xpcom.dll] for tracking.  The stack 
traces for this crash don't have the function symbols, so they're not very 
helpful, but here is some other info about this crash in the latest trunk 
builds for future reference:

xpcom.dll   39                     
     First BBID :28095490
     Last BBID  :28391350
     Min Runtime :0
     Max Runtime :45118
     First Appearance Date : 2001-03-21
     Last Appearance Date : 2001-03-28
     First BuildID : 2001032109
     Last BuildID : 2001032706

Stack Trace (just the top): 

         xpcom.dll + 0x3146a (0x60e3146a)  
         xpcom.dll + 0x30b2b (0x60e30b2b)  
         necko.dll + 0x859e (0x6073859e)  
         gkcontent.dll + 0x45919 (0x01265919)  
         gkcontent.dll + 0x4eda2 (0x0126eda2)  
         gkcontent.dll + 0x4f284 (0x0126f284)  
         gkcontent.dll + 0x86951 (0x012a6951)  
         gkcontent.dll + 0x86d18 (0x012a6d18)  
         gkparser.dll + 0x1b957 (0x603eb957)  
         .
         .
         .

        Source File :  line : 
     (28095490) Comments: copy paste stuff from a table created in 4.x and 
opened in 6.x andand crashed
     (28273800) Comments: starting up first time after install
     (28273846) Comments: starting up
     (28278916) Comments: hh
     (28278968) Comments: startup
     (28287178) URL: 
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1223549089
     (28287237) URL: 
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1223549089
     (28287237) Comments: stupid activation window
     (28287239) URL: 
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1223549089
     (28287935) URL: 
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1223549089
     (28295718) Comments: startup
     (28297548) Comments: startup
     (28302169) Comments: crash when launching on an existing profile.
     (28341739) Comments: crash on startup
     (28351968) URL: www.epost.de
     (28367595) URL: www.shg.dk
     (28367595) Comments: pressed reload
Keywords: crash, topcrash
Summary: Browser crashes on startup → Browser crashes on startup [@ xpcom.dll]
*** Bug 73281 has been marked as a duplicate of this bug. ***
This problem persists with the latest builds of Mozilla.  I'm running the Moz
0.9 nightly builds, and have had problems since 0.9 was released.  I start Moz,
the splash screen comes up, I get two "invalid procedure entry point" errors in
xpcom.dll, and the program proceeds to start normally after the errors are
dismissed.  The program does NOT crash/lock/terminate for me, it just whines.  I
am currently using build 2001060504 (downloaded it yesterday), and I still have
the problem.  I browsed bugzilla and most of the reports seemed to be for older
builds, and the bug was marked as FIXED; I just wanted to make sure that it was
re-opened for the more recent builds.  If I remember next time I start Moz, I'll
write down the exact error messages and post them in a follow-up.
--Dave
This problem persists with the latest builds of Mozilla.  I'm running the Moz
0.9 nightly builds, and have had problems since 0.9 was released.  I start Moz,
the splash screen comes up, I get two "invalid procedure entry point" errors in
xpcom.dll, and the program proceeds to start normally after the errors are
dismissed.  The program does NOT crash/lock/terminate for me, it just whines.  I
am currently using build 2001060504 (downloaded it yesterday), and I still have
the problem.  I browsed bugzilla and most of the reports seemed to be for older
builds, and the bug was marked as FIXED; I just wanted to make sure that it was
re-opened for the more recent builds.  If I remember next time I start Moz, I'll
write down the exact error messages and post them in a follow-up.
--Dave
OK, I got the error messages:

The procedure entry point ??_7nsLocalString@@6B@ could not be located in the
dynamic link library xpcom.dll.

The procedure entry point ??0nsInputFileStream@@QAE@ABV0@@Z could not be located
in the dynamic link library xpcom.dll.

Also, forgot to mention that I'm on Win2K.
--Dave
Dave Buckles: 
Pleas try it with a new profile (run "mozilla -profilemanger) and(or
delete your complete mozilla directory and reinstall mozilla.
If that doesn´t help open a new bug.


Dave - I think what is happening is that you have reinstalled over top of a 
previous installation directory. This means you probably have some obsolete 
DLLs in that directory, and that is causing a problem with the component 
registry (or related). If you sort the .dll and .xpt in your 'components'
subdirectory by date, you will probably see a few that are stale dated. Move
those to a temporary location, delete the file component.reg, and you will 
probably get rid of those (actually spurious) error dialogs. 


(As a general note, this bug has a horrible summary "crash on startup ( 
@xpcom.dll)". A crash in xpcom.dll is most often a null pointer dereference.
It's not particularly instructive that this causes a crash. What is of 
interest is what is above that on the stack.)
When I have had problems like this, I have been able to fix it by..
- uninstalling Mozilla
- removing the Mozilla directory from Program Files
- removing the Mozilla directory from my user's Documents and
Settings\user\Application Data directory
- reinstalling Mozilla

Maybe it's overkill, but ....
That fixed it.  Thanks.
Crash Signature: [@ xpcom.dll]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: