in message <20130408093145.GA3009@tinyCurrent>, wrote Matthias Apitz thusly... > > El día Monday, April 08, 2013 a las 11:04:41AM +0200, Patrick Lamaiziere > escribió: > > > Le Sun, 7 Apr 2013 13:38:55 +0200, > > Jens Schweikhardt <schwe...@schweikhardt.net> a écrit : > > > > > # We've had a thread about it in the forums, with a couple of > > > workarounds: # http://forums.freebsd.org/showthread.php?t=38627 > > > > > > Thanks for this helpful link. It contained the solution to my problem: > > > > > > 1) In about:config, set dom.ipc.plugins.enabled to false > > > 2) Exit and restart Firefox (really, just doing 1) did not work). > > > > Cool that works here too, nice. Thanks. > > I helped me as well. Can someone give a bit light of explanation > what the parameter does in detail and why it should be set to > 'false'? Thanks
An explanation on Adobe forum ... http://forums.adobe.com/thread/666110 32d reply ... ... The crash protection feature in Firefox 3.6 is enabled for certain plugins only. The four preferences that we modified here specifies four different out-of-process plugins. They are the the NPAPI test plugin, Adobe Flash, Apple QuickTime (Windows) and Microsoft Silverlight (Windows). These plugins are specified in a separate dom.ipc.plugins.enabled.<filename> preference by default is set to true. We can disable them by changing their value to false. And thus plugin-container.exe will not run. By default the preference dom.ipc.plugins.enabled is already set to "false". So, no need to touch it. The dom.ipc.plugins.timeoutSecs is also not important here as other values are false. Similar is on ... (skip to bottom) https://support.mozilla.org/en-US/questions/707085 (Also, I was reminded of "perlipc" pod related to inter-process communication in Perl.) -- _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
