
Silverlight plugin crashes when Netflix Progess bar used to advance or replay part of film
Netflix logs on OK and sucessfully starts amd runs films using Silverlight 5.1.20913.0 and the present up to date version of Firefox (26?) However if I attempt to fast forward or go backwards, using the Netflix slider, Silver light crashes with the following message "A Script on this page may be busy or it may have stopped responding etc. Script: http://movies.netflix.com/WiPlayer?movieid=70248289&trkid=13462100&tctx=-99%2C-99%2C87ddc936-30f9-44a2-952b-92aa6b28a381-660455:0" Processor at 100% load. Netflix runs faultlessly with IE 8 and Silverlight. BBC Iplayer etc run films OK OK I am running on windows XP service pack 3 on a HP a1429.uk PC with AMD Athlon 64 processor. I have installed the "AGP Programme may hang" patch in the registory for "LargePageMinimum" I have a Nvidia Geforce 8400GS video adapator running a composite video output to a TV in Dualview mode. Fault appeared after last Nvidia driver update via microsoft I have tried all the advice about running in Firefov in safe mode etc Looking for feedback
CARE
Disabling Plugin-Container is not a recommended solution
There is a danger that Firefox itself will become crashy if you disable plugin container.
even more importantly Adobe is not testing the new versions of Flash with the in-process configuration, which means that we're seeing crashes which are specific to in-process. {bug 769721]
Modified
Chosen solution
Unfortunately I am unaware of any security issues disabling plugin-container.exe. I only know it is a problematic area in Firefox as to handling the plugins such as Silverlight and Flash related issues. Mozilla has known about flash player crashes for years for example and o guess they cannot possible conceive that it is THEIR browsers plugin container causing the issue and always pointing the finger at flash. I am sorry I do not have the other answer for ya.
As far as the original article i referenced you could either used my regedit to implement as well, and does not require a machine re-boot unless you got some process stuck running you cannot kill.
I am glad i was able to get it resolved for you rather painlessly
Best Regards
Read this answer in context 👍 2All Replies (4)
Try to disable the pluginicontainer.exe and see if it works then.
If you are interested in seeing how, i posted a blog. It concerns more flash, but silverlight is a plugin as well, and all plugins by default use the plugin container to run inside of. try clicking on my name on the left and there is a link to my blog to explain how to do this. It takes literally 2 minutes to preform on a machine. The method of disabling the plugin container will not be posted on these forums for some odd reason.
Best Regards
Thanks, disabling the plugin container has worked round the problem. I can now use the slider to rewind and go forward on Netflix. The steady state processor load has dramatically reduced when playing a film on Netflix. It is now arround 30%, which is comparable with the BBC Iplayer and Flash. It was running arround 70% to 100% with the plugin container in use, even without moving sliders!.
A small point in the instructions, it was not clear whether the "O" in "_OOP_" was alpha or numeric (it is Alpha) and I had to reboot the PC before firefox recognised the enviroment variable and stoped the plugin container.
Does this have any impact on security as there must be a reason for the plug in container?
Regards
Chosen Solution
Unfortunately I am unaware of any security issues disabling plugin-container.exe. I only know it is a problematic area in Firefox as to handling the plugins such as Silverlight and Flash related issues. Mozilla has known about flash player crashes for years for example and o guess they cannot possible conceive that it is THEIR browsers plugin container causing the issue and always pointing the finger at flash. I am sorry I do not have the other answer for ya.
As far as the original article i referenced you could either used my regedit to implement as well, and does not require a machine re-boot unless you got some process stuck running you cannot kill.
I am glad i was able to get it resolved for you rather painlessly
Best Regards
Thanks,
The Problem is solved