Closed Bug 106434 Opened 24 years ago Closed 23 years ago

Plugins do not unload

Categories

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: ovvldc, Assigned: law)

References

Details

(Keywords: helpwanted)

When finishing with Mozilla in Turbo mode, the OJI (Java) plugin and probably the quicktime plugin, as far as I can tell from simple memory use, stay active and loaded in RAM. While quicklaunch is a very useful feature, the files that stay in RAM should perhaps be limited to what is needed to start a browser or mailnews window. The rest of system resources should be released IMHO. I found another unloading bug in 95130 which has a comment that may bear some light on this (Greg Miller 2001-08-13 14:12): >Correct me if I'm out-of-date or wrong, but I don't believe Mozilla currently >unloads any libraries once they've been loaded. It's also my understanding that >folders are never closed and unloaded, either. Putting aside what isn't needed might reduce footprint substantially.
i think this is wontfix fodder. Turbo is a compromise: sacrifice memory to increase load speed. Nothing about that compromise says we should make users pay again to load java.
What about time-based unloading? Unload plugins which have gone unused for X minutes. Do the same with folders. Push cache entries from memory to disk as well. After a couple hours, these things probably wouldn't be in memory anyway, and would have to be paged back in again. That could be slower than reloading the plugins anew. Should seperate bugs be filed?
if your os doesn't do that (swapping LeastRecentlyUsed app memory to disk) on its own buy a better one
What timeless said. We can't "unload" unless xpcom/componenter-manager, etc. let us. Setting target milestone to future.
Keywords: helpwanted
Target Milestone: --- → Future
confirming RFE.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 121345 has been marked as a duplicate of this bug. ***
*** Bug 141530 has been marked as a duplicate of this bug. ***
*** Bug 145013 has been marked as a duplicate of this bug. ***
I'm sure that the new turbo mode introduced by the checkin for bug 98673 has fixed this as well. Therefore closing out as fixed. Please re-open if I'm wrong.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
java isn't unloaded
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Is java unloaded when the browser is closed down w/o turbo? If not, then this is not a turbo bug. If so, then it is unloaded when the browser is closed down with turbo.
with build 20020528 it works fine. Java is unload when turbo is on.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
verified with trunk build 2002052809 build
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.