Bug 242307 – firefox trashing hdd sometimes

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 242307 - firefox trashing hdd sometimes

Summary:	firefox trashing hdd sometimes

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	firefox (Show other bugs)
Sub Component:
Version:	7
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Gecko Maintainer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-06-03 03:29 EDT by Marius Andreiana
Modified:	2007-11-30 17:12 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-06-03 14:01:03 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Marius Andreiana 2007-06-03 03:29:46 EDT

Sometimes firefox freezes and hdd is trashed for ~10 seconds. Then it resumes
normally (f7 test 4 and final F7).

My cache was at 25mb, set it to 5mb now. How could I debug this next time it
happens? 
lsof |grep firefox looks about the same during trashing and normal operation.

Thanks

Comment 1 Marius Andreiana 2007-06-03 03:40:50 EDT

I was out of space on hdd, this is replicable.

Please close if no fix is needed for firefox to behave better in this case.

Comment 2 Christopher Aillon 2007-06-03 14:01:03 EDT

Ah, out of space.  There's a bunch of bugs filed upstream at mozilla.org that
leads me to believe that this is just a case that isn't handled and has so many
bugs that there'd need to be a ton of work just to fix, and it would probably
need to be done by mozilla.org as the patch work would be just too large as
there are many areas that would need patching.

Going to close this I guess.  Thanks for the report and figuring out what was
happening.

Note You need to log in before you can comment on or make changes to this bug.