It would be a great start up performance improvement on machines with limited resources to be able to launch turbo mode only after Mozilla is used for the first time. Right now, a lot of processes compete for scarce resources during boot up, and Mozilla only adds extra time to the overall initial boot up time. Reproducible: Always Steps to Reproduce: 1. Enable Quick Launch 2. Reboot 3. It'll take noticeably longer to boot on older machine Actual Results: If Turbo mode is enabled, it takes some time for start up process to finish after power-on. Expected Results: Turbo mode will start only after a user explicitly uses Mozilla for the first time. Proposed enhancement: (In Preferences|Advanced) [X] Enable Quick Launch [X] Enable After First Use Only
i think this might be possible today by modifying your shortcut to do mozilla -browser -turbo [not sure]. [note that even if that is possible, it isn't a UI for it...]
Status: UNCONFIRMED → NEW
Ever confirmed: true
It seems like this would benefit users who sometimes don't use mozilla at all during an OS session (and hence want to optimize OS startup), but when they do use it, they launch multiple times (else there would be no point in having QL enabled. I'm not sure how common that is, and I'm concerned that we couldn't have it as default behavior, because it would cause extreme variarance in actual launch times. ->future
Target Milestone: --- → Future
I don't say it should be on by default either. It looks like a useful option for some. But as long as "mozilla -browser -turbo" continues to work (and it DOES work now - thanks timeless!), those of us with underpowered machines are happy campers.
"mozilla -browser -turbo" seems to crash almost every time Quick Launch tray icon is used. My guess, some resources get released based on Quick Launch preference, ignoring the fact that Quick Launch is actually running. W2K SP2, Build ID: 2002031104 (0.9.9)
*** Bug 136120 has been marked as a duplicate of this bug. ***
UI mentioned by Bamm Gabriana in bug 136120. Under Preferences|Advanced: -- Enable features that affect performance -- | [x] Enable Quick Launch | | (x) On Windows startup | | ( ) The first time Mozilla is run | ---------------------------------------------
Great idea! you got my vote :-) BTW, I couldn't find any bug that deals with the poor speed of the Turbo mode compared to the first Mozilla versions that had it. It used to be an instantaneous launch, but now it takes quite a few seconds. Prog.
A "LAZY" QUICK-LAUNCH A MUST for me to have Mozilla as a default browser. My machine's startup time is anyway slow and current quick-launch makes it much worse. I would love to have Mozilla as my default browser, but until "lazy" version of it is implemented, i simply can't afford it.
Barak: Please don't use features you don't understand. (clearing blocking)
Summary: [RFE] New Turbo preference: start after first use → New Turbo preference: start after first use
Mozilla already does something very similar under the Mac. If the user closes the last window, the program remains in the memory (like every HIG-compliant Mac application does). This RFE actually asks for an option that provides this behavior, under all OSes. Perhaps it would be better to change the summary of the bug to reflect this. Prog.
I was going to report my bug, then, I found this after search. Now, I add my report as a comment here and vote to this bug: ->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I wish quicklaunch of mozilla load (and remain in ram) with the first session of mozilla, not with Windows startup. Regards, Bahram Alinezhad, Rudehen, Tehran, Iran. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<-
*** Bug 256309 has been marked as a duplicate of this bug. ***
Quicklaunch/Turbo Mode is no longer supported in Seamonkey 2 and Seamonkey1.X is in the maintenance mode (fixing only security bugs)
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Component: QuickLaunch (AKA turbo mode) → QuickLaunch (AKA turbo mode)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.