Closed
Bug 270253
Opened 20 years ago
Closed 19 years ago
crash if run out of disk space
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 257048
People
(Reporter: koscio, Assigned: bugzilla)
References
()
Details
(Keywords: stackwanted)
Attachments
(1 file)
|
38.33 KB,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041116 Firefox/0.9.1+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041116 Firefox/0.9.1+ If you run out of disk space, where the cache is stored, the browser will crash on various situations. The quick way: View->Page Source Reproducible: Always Steps to Reproduce: 1. Start up Firefox 2. Open some web page, google.com is ok 3. Store some data on your disk, leave 0-2kb free disk space 4. to crash Firefox: View->Page Source Actual Results: Firefox crashed Expected Results: Firefox should check up available disk space.
if you can get talkback to run and have time to play with this, the best approach would be to quota the mozilla profile directory or the cache directory and then crash a bunch of times, reporting the incident ids here.
Keywords: stackwanted
I can crash firefox always, but talkback.exe doesn't start or crash. Luckily 1 time it started.
Comment 4•20 years ago
|
||
we need only the Talkback ID, not the talkback summary file for that crash.
(In reply to comment #4) > we need only the Talkback ID, not the talkback summary file for that crash. can't give any Talkback ID, beacause there are no incidents in talkback.exe. Also, talkback agent hardly ever opens up after firefox crash.
This bug exists also under Linux for the version 1.0, and the crash occurs
before the window appears.
strace gives the result :
open("/home/pappy/.firefox/default/tynd49ma.slt/XUL.mfasl",O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE,
0644) = 34
etc...
write(34, "\0\0\0\0\0\0\10]\376\355\276\347j\t\346\212\2367y\270\0"..., 65536) =
-1 ENOSPC (No space left on device)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
The 'write' system call is done more than 4500 times!
Comment 7•20 years ago
|
||
I thought it was normal for XP, or any Windows OS, to crash if the system runs out of disk space. (no flame intended). Just make sure you have disk space available and you won't have problems.
Comment 8•19 years ago
|
||
(In reply to comment #6) > This bug exists also under Linux for the version 1.0, and the crash occurs > before the window appears. > strace gives the result : > > open("/home/pappy/.firefox/default/tynd49ma.slt/XUL.mfasl",O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, > 0644) = 34 > > etc... > > write(34, "\0\0\0\0\0\0\10]\376\355\276\347j\t\346\212\2367y\270\0"..., 65536) = > -1 ENOSPC (No space left on device) > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > > The 'write' system call is done more than 4500 times! > Same here running Debian. It crashed then couldn't be restarted. Same strace more or less. Luckily strace is here else I would have had no clue (it's my home partition that was full, /tmp was OK).
(In reply to comment #8) > (In reply to comment #6) > > This bug exists also under Linux for the version 1.0, and the crash occurs > > before the window appears. > > strace gives the result : > > > > > open("/home/pappy/.firefox/default/tynd49ma.slt/XUL.mfasl",O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, > > 0644) = 34 > > > > etc... > > > > write(34, "\0\0\0\0\0\0\10]\376\355\276\347j\t\346\212\2367y\270\0"..., 65536) = > > -1 ENOSPC (No space left on device) > > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > > > > The 'write' system call is done more than 4500 times! > > > > Same here running Debian. It crashed then couldn't be restarted. Same strace > more or less. Luckily strace is here else I would have had no clue (it's my home > partition that was full, /tmp was OK). > > I also experience this bug when the drive that the Cache is stored on has no free space. I am using XP. If I make free space on that particular drive, then the browser stops crashing. I am using 1.0.6
Comment 10•19 years ago
|
||
*** This bug has been marked as a duplicate of 257048 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•