Closed
Bug 730662
Opened 13 years ago
Closed 13 years ago
Firefox takes a lot of time to delete files in Cache.Trash before startup
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 701909
People
(Reporter: piyush_soni, Unassigned)
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11
Steps to reproduce:
Nothing criminal. Just started Firefox again (by the way, Firefox had crashed before this for some reason, but that's fine, applications do crash. It's not about that. )
Actual results:
Nothing happened :). Have been waiting for past <strong> 24 minutes </strong>, Firefox is still doing something even without loading the main window. Opened Google (R) Chrome to sing in and log this bug - and I don't love that.
Before you jump on to close the bug saying the ages old thing : "Oh! That's not firefox. That's your add-ons!". No. It isn't. It is Firefox, and I have proofs. Had just opened SysInternal's Process Monitor to find out if there's really an extension which is playing up. Saw a long list of file transactions, where you are doing 'something' with the "Cache.Trash" folder of my default profile for past 24 minutes! I think this is done even before beginning loading the extensions right? Attached image is a screenshot of Process Monitor which shows the same.
No, starting with a clean profile is NOT a solution. It is just a work around.
And like previous bugs of this kind, please do not close this with WORKSFORME tag. Really? WORKS FOR ME? I am a software developer too and this could probably be the most ridiculous type of a bug closing flag :P
Expected results:
Firefox should have started instantly - just like Chrome does EVERY TIME. I don't know how they manage to do it, even though most of their original stuff has been stolen from Firefox.
This has been the same since Firefox 2 or 3!
I say, none of the users would mind if for a few major releases you don't do anything, but just fix the startup time problem and memory hogging overnight (which was claimed to be greatly improved a few releases back). These are like the very basic ones!
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 2•13 years ago
|
||
You're a software developer, so you should know bug reports aren't a place to complain but to report problems. Please stop writing thirty lines of useless text when you can write only a line, otherwise people will not take your bug seriously.
WORKSFORME isn't a ridiculous closing flag, there are guidelines that say when you can close a bug with such flag. Read here: https://developer.mozilla.org/en/What_to_do_and_what_not_to_do_in_Bugzilla#Resolving_bugs
The Crash.Trash folder was probably created after the crash you mentioned. Now Firefox is deleting every file in that folder, before renaming it to Crash. Could you check what's the size of the Crash.Trash folder? Could you try deleting it manually?
Status: RESOLVED → UNCONFIRMED
Component: Untriaged → Networking: Cache
Product: Firefox → Core
QA Contact: untriaged → networking.cache
Resolution: DUPLICATE → ---
Updated•13 years ago
|
Summary: FIX Firefox start up time! → Firefox takes a lot of time to delete files in Crash.Trash before startup
Reporter | ||
Comment 3•13 years ago
|
||
I knew this would come up(the software developer thing), but anyway that's fine.
Justification(useless w.r.t. the bug):
I just wanted to make sure this bug is not closed for reasons not appropriate, which has happened in the past. For example, a very similar bug in Firefox 2.0 was closed with this very flag, when
a). the current stable release became 3.x.
b). The QA could not reproduce it in that Firefox 3.x
These are not enough criteria to close a bug in my opinion. We tag them with something like FIXLATER.
Information relevant to the bug:
The folder in question was Cache.Trash, not Crash.Trash (though it does not matter much). I cannot see the size of it now, as it seems it got completely deleted finally :(. You said it gets renamed to something else? Is there any other place where I can go and find the size? I do not see this folder anymore in my FF profile.
Comment 4•13 years ago
|
||
Yes, it was Cache.Trash :D
AFAIK the files in that folder gets deleted after a Firefox crash, so now that you haven't it in your profile folder, it's impossible to check what was its size.
However there were some bug reports of slow cache clearing, that were resolved by bug 670911 and bug 674869, I'm CCing jduell that should know things better than me.
In the meantime could you give more informations about your configuration? (Operating system (Windows 7, right?), Firefox version (10, right?), filesystem where your profile directory resides)
Reporter | ||
Comment 5•13 years ago
|
||
Yup.
Firefox 10.0.2
Windows 7 x64,
Filesystem: NTFS
Installed shell extensions that might matter (/interfere): Tortoise SVN.
Antivirus : AVG Free.
Firefox User characteristics: Generally keeps MANY tabs open :P , saves tabs.
Firefox Add-ons (though they should not matter):
Adblock Plus, DivX Web Player, Firebug, Greasemonkey, Lazarus: Form Recovery, Pixlr Grabber, Stylish, Xmarks
Plugins:
Many lengthy names :(
Severity: normal → major
Reporter | ||
Updated•13 years ago
|
Summary: Firefox takes a lot of time to delete files in Crash.Trash before startup → Firefox takes a lot of time to delete files in Cache.Trash before startup
The changed summary now matches bug 701909 comment 3
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → DUPLICATE
Comment 7•13 years ago
|
||
Thanks for this bug, even if a DUP, there is useful info in here.
You need to log in
before you can comment on or make changes to this bug.
Description
•