Problems with silverlight in firefox
I should add that there are issues besides memory consumption. My problem is that I don't know the architecture of the thing, so I would have to spend a lot of time learning internals - something I would have no use for once I found and fixed the bug. If I had time to waste, I would look into it myself and try and come up with a fix. Yet they all hang in a sort of limbo waiting for reasons that are not obvious. As I dig around, I find more and more duplicates of what is probably the same issue - some of them (including the one I posted (470481) have stack traces where the allocations took place). The repro steps are straightforward enough. I have to admit that it amazes me that this issue is still open as well. But, why in the world dom.max_script_run_time don't work here? Because, you see, this is vMicrosoftv and vSilveLightv and the rest. I understand that this is more than political issue than programmatic.
![problems with silverlight in firefox problems with silverlight in firefox](https://ubuntuhandbook.org/wp-content/uploads/2013/08/silverlight-chrome-linux.jpg)
Some of the statistics can be found in the related Bug id 516202 ģ) The question is. Summary, if more tabs and more plugins in FF instance, than more quickly memory leakage can be seen. The more plugins installed in FF the more path will be passed through file system and registry. G) The more tabs contained Silvelight.js opened the more will be activity (each script working independently). Add filter: "Process Name, contains, firefox.exe, Include" Į) Enjoy the file and registry activity produced by the FF į) Silverlight.isInstalled() function fail, thus, parent function Silverlight.WaitForInstallCompletion() get stuck in the try.catch statement, which will be calling again every 3sec SilverLight.isInstalled() function and, worst of all, (), that caused continuous activity of FF.
#Problems with silverlight in firefox install#
Steps to reproduce (successfully confirmed on):Ī) Clean install (as well as already installed) Windows XP x32 (any SP's), Windows Server 2008 x32 (any SP's), Windows 7, Windows Server 2008 R2 圆4 ī) Clean install of any of the released builds of FF from 3.0.x to 3.5.x Ĭ) Open in FF (at this step, out of dozens PC&FF installations, SilverLight plugin installation offer cannot be seen) ĭ) Open Process Monitor (ProcMon, By Mark Russinovich and Bryce Cogswell, can be found here: ). SilverLight control script can be found at a whole *. site.
![problems with silverlight in firefox problems with silverlight in firefox](https://www.brighthub.com/ezoimgfmt/img.bhs4.com/a3/b/a3bda74231931d9be0ca640473eb6789b41c5116_large.jpg)
Probably the script can further reduced and getting the Silverlight out.ġ. The memory usage did not go down and continuing surfing as normal, was on a much higher memory footprint (around 200MB, while normally I surf with 140MB). Then I opened a new tab and closed the leaking tab. I waited until FF grew from 45MB to 180MB. I loaded the attachment without any other tabs. I am pretty sure FF is, because the memory is not reclaimed after closing the tab. The question remains whether the script is leaking (building huge datastructures) or FF. I increased the speed to 10 times a second, showing a much faster leaking (note, leaking may occasionally stop for a while). In the attachment, I copied the script inline without references.
![problems with silverlight in firefox problems with silverlight in firefox](https://www.worden.com/assets/images/support_articles/firefox_plugins.png)
If the user has no Silverlight or turned it off, it will continue leaking. If not it waits 3 seconds and looks again. Details The leak is in the silverlight detection script: It could be Normal, but it could be Critical, as well. I'm not sure what is the severity of such issue. Check the amount of consumed memory by firefox. Open the given above 5 urls (one or more then one of them is causing the problem, however I'm not sure which one)ģ.
![problems with silverlight in firefox problems with silverlight in firefox](https://www.timecockpit.com/media/1f61e97e-5711-4fed-b674-96c53e0f39d8/YYk_5w/time_cockpit/blog/2015/04/chrome-enable-npapi.png)
On Monday morning according to Windows Task Manager, memory usage: 1.4GB !įrom my perspective, this is a quite severe memory leak.ġ. I left my firefox open over the weekend with the following 5 urls open into tabs into it: