User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1 Build ID: 20120731150526 Steps to reproduce: Didn't notice that my RAMDISK did not startup. FF15b3 main window never displayed; although password-window asked for password and it was correctly entered. FF in taskmgr ! Plugin-container and flash tasks did not show up in taskmgr. Had to kill FF. Tried twice. Safemode worked OK. FF15b3 main window no show with disk letter missing. Actual results: FF15b3 main window no show with disk letter missing. Manually killed FF in taskmgr. Expected results: If RAMDISK missing, FF should have used default disk (maybe) and main FF window should have been visible.
This can only happen of you have a reference to this drive and only you can tell us what Firefox would load from that drive.
It's labelled E:\ and is a ramdisk for FF's disk cache. It's also, at shutdown and bootup, saved and retrieved as an image file on the HD, respectively. Pretty standard stuff. In the past, when the ramdisk failed, FF would still fully bootup properly but just use regular ram (Memory cache device) but not cache.disk (Disk cache device)
Can you specify "In the past" a little bit more precise ?
Component: Untriaged → Networking: Cache
Product: Firefox → Core
Summary: FF15b3 main window no show with disk letter missing → Startup hang if drive/location for the disk cache is missing
Been using ramdisk on all official releases since before early 2011 with no problem; and FF15 nightly, aurora, beta. Note: when ramdisk at startup became reliable then i wouldn't see this bug. Only rarely did ramdisk (i.e. E:\) not load properly in the past year.
Well now it works ok. I just now tried to simulate it by using an invalid drive letter f:\ and FF15b3 booted fine. I even tried it via the profile manager. In the past I had limited the amount of browser.cache.disk to 100MB (smaller than the ramdisk). Recently I set it to automatic while trying to debug the non-full startup; and to get it to fully boot.
Well now it sometimes hangs at startup even if disk-cache memory (ramdisk) is there. After 5 minutes of no FF 15.0.1 window, and it consuming 250 MB of ram, I then clicked on starting FF (shortcut) again and it may awake FF. After 3 secs, I got 2 FF windows. Note: 45 addons. Minimal cpu used during the FF window hang. Very FF slow ram-usage increase during hang.
(In reply to mike from comment #6) > Well now it sometimes hangs at startup even if disk-cache memory (ramdisk) > is there. One would think that unrelated to your original report Do you still see the original problem?
Closing this bug as incomplete due to lack of response from the reporter. Feel free to reopen the bug if the issue still reproducible in latest release.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
In addition, WFM after browser.cache.disk.parent_directory as "Z:\" in Fx45b5 Win10.
You need to log in before you can comment on or make changes to this bug.