1011875 - There seems to be some kind of conflict with the FlashPlayerPlugin.

Status: RESOLVED WONTFIX

(SeaMonkey :: General, defect)

Description

[Manny]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 (Beta/Release)
Build ID: 20140428215944

Steps to reproduce:

While watching a video the pop-up will come up stating that the plugin has stopped, it happens every day, many times.



Actual results:

A pop-up comes up to say the plug-in has stopped working, all video is lost, I have to bounce the browser. This has been happening for a long time. Also, Seamonkey, and Firefox for that matter, seem to have a problem managing memory, at one point it was up to 1.5GB. I am using Windows 7, and have the latest version of Seamonkey.


Expected results:

Nothing, there should not be a conflict with the FlashPlayer Plug-in.

Comment 1

[therube]

> I have to bounce the browser

What is "bounce"?
Anything like "kill"?
If so, would think killing plugin-container.exe would be sufficient.

Does FF have the same troubles with Flash?
 
 
http://kb.mozillazine.org/Flash#Troubleshooting

http://kb.mozillazine.org/Issues_related_to_plugins

http://kb.mozillazine.org/Firefox_crashes

http://helpx.adobe.com/flash-player/kb/common-problems-flash-player.html
 
 
> problem managing memory, at one point it was up to 1.5GB

Could be an issue, or could just be because of the content you had loaded (IOW could be "normal", expected). In any case, if not directly unrelated to the Flash issue, should be brought up elsewhere, mozillazine.org perhaps.

Comment 2

[Manny]

"bounce" means closing Seamonkey and starting it up again. Yes it happens with FireFox as well, and it has happened with all versions of all, including FlashPlayer, I update every time a new version is available with hopes that the problems will go away.

By the way, the same issue happens on my wife's computer, which is running Windows 8.

Comment 3

[therube]

So are there specific videos that cause the issue?

Do you & your wife use the same type/brand/CPU/video of computers?

Comment 4

[Manny]

No, these are not specific videos and no we don't use the same type.brand/CPU of computers. Also, this same issue has happened with older computers as well.

Comment 5

[Manny]

Attachment: Show memory usage of Seamonkey

I do have several tabs open, but even when I don't, the memory seems to climb.

Comment 6

[Philip Chee]

(In reply to Manny from comment #5)
> Created attachment 8426985 [details]
> Show memory usage of Seamonkey
The screen shot of windows task manager isn't very useful

Instead go to about:memory , click on the :"Measure" button.
Copy and paste the report via the attachments link in this bug.

Comment 7

[Philip Chee]

The Flashplayer plugin runs in a separate process, so it should show in the Windows Task Manager as plugin-container.exe. You probably don't need to bounce SeaMonkey, rather you should kill the plugin-container.exe process in the Task Manager and then reload the page in SeaMonkey.

Comment 8

[Manny]

"Instead go to about:memory"...How do you get to that? I looked around and could not find it, am I missing a plug-in?

If will try your suggestion of stopping the Flashplayer next time it happens, which should be sometime today, but if my memory serves me well, I have done that, and when I do I loose the plug-in and the only way to restore it is to bounce (stop/start) Seamonkey.

One more point, this doesn't happen when I use "IE", but I dislike IE very much so I stick with Seamonkey.

Comment 9

[Philip Chee]

Your locationbar (urlbar the box where you type in urls like "https://bugzilla.mozilla.org/show_bug.cgi?id=1011875")

Type "about:memory" in the box (without the "quotes")

Also it might be worth checking if there is a newer version of the adobe flash player.

Comment 10

[Manny]

(In reply to Philip Chee from comment #7)
> The Flashplayer plugin runs in a separate process, so it should show in the
> Windows Task Manager as plugin-container.exe. You probably don't need to
> bounce SeaMonkey, rather you should kill the plugin-container.exe process in
> the Task Manager and then reload the page in SeaMonkey.

I have tried that, and the plug-in does not get restarted, I still have to stop/start Seamonkey. I am not sure if this information gets to the developers, but it seems to me the issue is not so much with Flashplayer as a problem with Memory Management in Seamonkey...I could be wrong, but that is what it looks like. I understand that Seamonkey is written in C++? If so, it may be that memory is not being released properly? Just guessing...

Comment 11

[Frank-Rainer Grahl (:frg)]

The Flash plugin is no longer supported and will be blocked in 2.53.7