Memory leak in HTML5 Extension for Windows Media Player Firefox Add-on


Recommended Posts

HTML5 Extension for Windows Media Player Firefox Add-on leaks memory like a sieve.

My memory usage jumps over to 1.5G over a period of two days when I have this addon enabled.

After I disabled the addon my firefox memory usage has dropped to average around 200MB.

Anyone else notice this?

i leave Firefox open for days even weeks and it does not grow that big but then i limit what extensions/plugins it uses. also why are you using that plugin? is there any need for it? i would think not.

  On 30/01/2011 at 18:52, figgy said:

Yeah I leave I never close the browser unless I need to restart the system.

So it may be open for several weeks.

Firefox always will start to eat RAM like a madman when opened for several hours or days, even without a tab open, just hanging there.

4.0 Beta 8 through 10 (that's when I jumped to v4) don't seem to be doing this.

You should close the browser when its not needed. The cold start is feeling is better.

Its sad, but the developers don't seem to give this the priority it deserves.

  On 30/01/2011 at 19:41, ajua said:

Firefox always will start to eat RAM like a madman when opened for several hours or days, even without a tab open, just hanging there.

4.0 Beta 8 through 10 (that's when I jumped to v4) don't seem to be doing this.

You should close the browser when its not needed. The cold start is feeling is better.

Its sad, but the developers don't seem to give this the priority it deserves.

Why? I should be able to keep any browser open 24/7 for as long as I want. I don't get it ? Why can't I keep Firefox, Opera, Chrome, IE, Safari, etc open for days, weeks, or months ? I never shutdown my pc.

  On 01/02/2011 at 16:47, Educated Idiot said:

I rarely shut down my PC but I always close the browser when I'm not using it.

Reason #1: Security

Winkey+L

  Quote

Reason #3: Energy/resources

Holding x programs in RAM doesn't take any more energy then holding x-1 does.

  On 01/02/2011 at 16:47, Educated Idiot said:

I rarely shut down my PC but I always close the browser when I'm not using it.

Reason #1: Security

Reason #2: Habit

Reason #3: Energy/resources

Hmm I don't see any of those being a problem. Sometime is fishy around here if everyone closes their browser after using it all the time. You shouldn't have to do it period.

am i the only one who notices the FORUMS over at http://www.themortalkombat.com/ eat up more and more and more RAM everytime you refresh the page? (like load up a random topic in the forums and just hit the F5 key, let it load, hit F5 key again, if you keep doing that it can jump up RAM use quite quickly when most sites are fine.)

it does this in Stable v3.6 Firefox and the Firefox 4 BETA's.

  • 2 weeks later...

Microsoft certainly had me fooled into thinking they gave a damn about ideas in this world not directly related to themselves. This Add-on was a promising concept, but like everyone else I had to disable it just to do day to day things in Firefox. That's OK though since I couldn't find a freakin useful task for it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 10 KB5062649 fixes Extended Security bug, unresponsive systems, and more by Sayan Sen Microsoft has released today the non-security preview update (also known as the C-release) for Windows 10. The update, under KB5062649 and Build 19045.6159, fixes some major bugs including one for Extended Security Updates (ESU), unresponsive systems, Secure Boot, and more. Since this is a preview update for next month's Patch Tuesday it is an optional release. Microsoft says that users reported that the ESU wizard would not work correctly when they tried to use the option to extend support for Windows 10 for another year; this bug should be fixed now. The company has also fixed "stability issues" with this release as it resolves problems in the core file system. Affected users reported unresponsive systems since the May 2025 Patch Tuesday. There are other improvements as well. The full changelog is given below: ​​​​​[Extended Security Updates] Fixed: An issue impacting the Windows 10 Extended Security Updates (ESU) enrollment wizard. Some users experienced a problem where clicking “Enroll now” caused the wizard window to open, begin loading, and then close unexpectedly. This occurred due to incomplete app registration, which prevented the wizard from loading correctly. This update addresses that issue to ensure a smoother enrollment experience. [Mobile Operator Profiles] Updated: Country and Operator Settings Asset (COSA) profiles. [Secure Boot] New! Adds the ability to deploy SKUSiPolicy VBS Anti-rollback protections through the Secure Boot AvailableUpdates registry key. [Core File Systems] Fixed: An issue observed in rare cases after installing the May 2025 security update and subsequent updates causing devices to experience stability issues. Some devices became unresponsive and stopped responding in specific scenarios. [Input] Fixed: A known issue with the Microsoft Changjie Input Method. Users were unable to select words after a recent update. Fixed: A known issue when searching for an emoji in the emoji panel. After a recent update, the search always returns no results. Fixed: An issue in which phonetic input methods, including the Hindi Phonetic Input keyboard and Marathi Phonetic keyboard do not work correctly after a recent update. You can find the official support article here on Microsoft's website.
    • Are there any foldable phones where you can't actually see where the hinge is on the screen? If not, I definitely will never use one until that's possible. That makes the camera cutout look good by comparison.
    • Recall has a completely different purpose and feature-set than Timeline though. It shares some similarities, sure, but Recall isn't an evolved version of Timeline.
    • Yeesh, still a privacy nightmare.
    • That doesn't contradict what I said though. I benchmarked some games some time ago and the actual performance hit came from VBS, not HyperV. With HVCI off, VBS was only knocking off a few FPS on average for me.
  • Recent Achievements

    • Week One Done
      SmileWorks Dental earned a badge
      Week One Done
    • Community Regular
      vZeroG went up a rank
      Community Regular
    • Collaborator
      Snake Doc earned a badge
      Collaborator
    • Week One Done
      Snake Doc earned a badge
      Week One Done
    • One Month Later
      Johnny Mrkvička earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      Michael Scrip
      197
    3. 3
      ATLien_0
      193
    4. 4
      +FloatingFatMan
      131
    5. 5
      Xenon
      122
  • Tell a friend

    Love Neowin? Tell a friend!