Closed
Bug 235959
Opened 20 years ago
Closed 19 years ago
mozilla hangs with 100% cpu on bare address in url window [@ nsGnomeVFSProtocolHandler::Init]
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: jim.brown, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
Attachments
(2 files)
User-Agent: Build Identifier: Mozilla/5.0 (X11; U; OSF1 alpha; en-US; rv:1.7b) Gecko/20040228 Enter a value in url window (e.g. cstars.rsmas.miami.edu). mozilla is now hung using 100% cpu. Reproducible: Always Steps to Reproduce: 1. enter a bare address in url window: e.g. cstars.rsmas.miami.edu 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. http://www.realsoftware.com/download/alphas_betas/REALbasic551fc1MacClassic.sit 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.
Traceback looks the same as the first attachment. This appears to be the same problem. Download link is http://download.macromedia.com/pub/freehand/updates/11_0_2/mac/fhmx_1102_updater.dmg
This is really a crash (if I use the debugger). It is only a hang because mozilla does not successfully trap the SEGV fault.
Updated•20 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]
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•20 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: --disable-gnomevfs
Blocks: gnomevfs
--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.
Comment 7•20 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.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 8•19 years ago
|
||
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 9•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•13 years ago
|
Crash Signature: [@ nsGnomeVFSProtocolHandler::Init]
You need to log in
before you can comment on or make changes to this bug.
Description
•