MozillaZine

Killing Flash Player Process causes SM Crash

Discussion of bugs in Seamonkey
Zerebralus
 
Posts: 100
Joined: September 3rd, 2014, 7:20 am

Post Posted January 5th, 2015, 11:10 am

Just noticed this issue with Version 2.32 (betas), also get some crash reports (sent).

Maybe this issue causes plugin container failure (not sure at all)

therube

User avatar
 
Posts: 18784
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted January 5th, 2015, 12:27 pm

Last few crash report URLs (about:crashes) ?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Zerebralus
 
Posts: 100
Joined: September 3rd, 2014, 7:20 am

Post Posted January 5th, 2015, 1:37 pm


Zerebralus
 
Posts: 100
Joined: September 3rd, 2014, 7:20 am

Post Posted January 16th, 2015, 9:59 pm

same again with the final Version 2.32

Just ended my browser game but the flashplayer plugin still uses about 400 MB. then (in the taskmanager) killing the flashplayer process... also crashes the browser.

Then changed "dom.ipc.plugins.enabled" in the browser config from true to false and then tried again to kill the flashplayer process. Only the flashplayer in the browser (game) window normally crashed. But not the browser as before...

so what's wrong?

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted January 17th, 2015, 7:26 pm

Why force-crash Flash at all? If you leave it alone it should close out when it's done doing it's thing in the background. It usually takes a minute or so... may take longer for heavy use like that.

Also, when you disable dom.ipc.plugins.enabled you shouldn't even see plugin-container as Flash will not be in a separate process so you can't force-crash Flash out. Note that running in that mode is not recommended because if Flash crashes it will *definitely* take out SeaMonkey.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

Zerebralus
 
Posts: 100
Joined: September 3rd, 2014, 7:20 am

Post Posted January 18th, 2015, 1:42 pm

the curious thing is... although dom.ipc.plugins.enabled is set to false, the plugin container is still running in the taskmanager

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted January 18th, 2015, 1:56 pm

Plugin-container will open on restart as part of a crash recovery. So if you force-crash the browser, next time it opens plugin-container will also open. I've seen cases where that may cause SeaMonkey to immediately crash out, but that involved running out of page-file space. Ending the crash-recovery plugin-container process has absolutely nothing to do with closing Flash. If you close and open SeaMonkey normally, you should not see plugin-container with dom.ipc.plugins.enabled false. (But of course you won't have crash-protection)
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

therube

User avatar
 
Posts: 18784
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted January 19th, 2015, 8:20 am

dom.ipc.plugins.enabled is set to false

If that is the case, then why would you not expect killing Flash to cause SeaMonkey to crash?

The is precisely the purpose of out-of-process plugins, to prevent a Plugin crash from taking down the browser.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Zerebralus
 
Posts: 100
Joined: September 3rd, 2014, 7:20 am

Post Posted January 19th, 2015, 1:18 pm

First Seamonkey 2.31 tried again without problems when the flash kill process. Then online update on Seamonkey 2:32 and the same tried. This time with no problems. Only the window with the Flash Game crashed (as expected)

So I guess that a file in the profile was probably a mistake because I had started with an almost new profile.

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted January 20th, 2015, 2:05 pm

Right. Once you start having crashes, or are force-crashing the browser you greatly increase the chance of corrupted files which can lead to further instability. This is one reason why it's really not recommended to force-crash programs.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

Return to SeaMonkey Bugs


Who is online

Users browsing this forum: No registered users and 3 guests