Closed
Bug 536496
Opened 15 years ago
Closed 15 years ago
Random soft-crashes, probably related to memory usage bug.
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: goatboy100, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.6) Gecko/20091215 Ubuntu/9.10 (karmic) Firefox/3.5.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.6) Gecko/20091215 Ubuntu/9.10 (karmic) Firefox/3.5.6 Firefox sporadically crashes without any warning, without any errorsö it just disappears. Reproducible: Sometimes Steps to Reproduce: 1.Launch FF 3.5 2.Browse for an extended period of time without closing the session 3.leave it idle for a little while, and it'll disappear! Actual Results: Firefox completely disappears, and, when relaunched, loads all tabs that were open as though it were told to save the tabs and quit. Expected Results: It should stay open until exited by the user! <Main> <Addons.lst> DownThemAll; FireFTP; </Addons.lst> <HardwareSpecs> CPU = 2.4Ghz */performs like 550Mhz/*; RAM = 1GB DDR400 */Pagefile.Present = False/*; OS = Windows XP Home (32 bit); </Hardware Specs> </Main>
Comment 1•15 years ago
|
||
Reporter, please provide a crash ID. This isn't enough info Resolved Incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Comment 2•15 years ago
|
||
That's just it; there IS no crash ID or other info given! No errors, no warning, nothing! It just disappears! Exact (FF) version is 3.5.6
Status: RESOLVED → VERIFIED
Resolution: INCOMPLETE → WORKSFORME
Reporter | ||
Comment 4•15 years ago
|
||
It's impossible to get my mom (the main user of that computer) to leave a command prompt open to get crash info; she always closes the command prompt (and, by extension, that instance of FF), and restarts FF using one of the desktop shortcuts. I've already thought of that, tried it, and failed. Are there any internal commands (like the ones used to start FF in safe mode\profile selection mode, or get a stack trace) that you know of? If there aren't any,I've got an idea (might not be a feasible one) for a debugging code snippet that should help in cases like this one.
you can write a shell script which does something like: firefox >> ~/firefox-out.log 2>> ~/firefox-err.log & or something, the exact details of how the script would work would depend on your shell. And I'm too tired to figure out the proper syntax.
You need to log in
before you can comment on or make changes to this bug.
Description
•