mozilla hangs with 100% cpu on bare address in url window [@ nsGnomeVFSProtocolHandler::Init]



15 years ago
8 years ago


(Reporter: jim.brown, Unassigned)


({crash, regression})

crash, regression
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)


(crash signature)


(2 attachments)



15 years ago
Build Identifier: Mozilla/5.0 (X11; U; OSF1 alpha; en-US; rv:1.7b) Gecko/20040228

Enter a value in url window (e.g.
mozilla is now hung using 100% cpu.

Reproducible: Always
Steps to Reproduce:
1. enter a bare address in url window: e.g.
2. see mozilla hung with 100% cpu usage
3. there is no #3

This seems to be a recent regression.

There is a similar kind of 100% cpu hang if I enter a file download in the url
window, e.g.

The UI is hung but the file download appears to be progressing.
I did not wait to see if the UI would come back to life after the download finished.

Comment 1

15 years ago
Created attachment 142706 [details]
Traceback after entering cstars... in url window

Comment 2

15 years ago
Created attachment 142707 [details]
Traceback on file download attempt

Traceback looks the same as the first attachment.
This appears to be the same problem.
Download link is

Comment 3

15 years ago
This is really a crash (if I use the debugger).
It is only a hang because mozilla does not successfully trap the SEGV fault.


15 years ago
Keywords: crash, regression
Summary: mozilla hangs with 100% cpu on bare address in url window → mozilla hangs with 100% cpu on bare address in url window [@ nsGnomeVFSProtocolHandler::Init]

Comment 4

15 years ago
Trunk build on 040227 15:56 does not have this problem.
Trunk build on 040228 11:03 has this problem.
Trunk build on 040301 16:24 still has this problem.

Comment 5

15 years ago
this is not a problem for me under linux.  nsGnomeVFSProtocolHandler is an
optional extension that was added just recently (See bug 233305).  perhaps there
is some problem with OSF/1 that prevents it from working correctly?  who
generated the OSF/1 build, and what options were used to compile it?  perhaps
this option should be specified:

Blocks: 233305

Comment 6

15 years ago
--disable-gnomevfs does get rid of the crash but this does not resolve the
question of why mozilla crashes with gnomevfs.  I will see if I can get anywhere
with the debugger.


15 years ago
Blocks: 237822

Comment 7

15 years ago
The crash may come from the fact that glib-1.2 (from gtk) and glib-2.0 (from
GnomeVFS) are used at the same time. Can you confirm?
See bug 238374.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
Crash Signature: [@ nsGnomeVFSProtocolHandler::Init]
You need to log in before you can comment on or make changes to this bug.