bugGnash - The GNU Flash player - Bugs: bug #16779, plugin doesn't kill its childs

 
 

bug #16779: plugin doesn't kill its childs

Submitted by:  James Ausmus <ausmusj1>
Submitted on:  Wed 07 Jun 2006 05:23:47 PM UTC  
Votes:  100  
 
Category: NoneSeverity: 3 - Normal
Release: NoneStatus: Fixed
Privacy: PublicAssigned to: None
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Tue 26 Sep 2006 01:45:07 PM UTC, comment #7:

feel free to open a new item for performance problems.

Sandro Santilli <strk>
Project Member
Tue 19 Sep 2006 05:41:30 PM UTC, comment #6:

OK, the children not dying seems to be fixed - for the most part. When I close the tabs or the browser, the gnash processes do shut down. However, when I closed the myspace.com tab, the entire browser window refused to repaint at all, until I had minimized then restored the browser window. I don't know if this is related or not - I also don't know if it's repeatable (I'm at work, so my testing capabilities are rather limited at the moment) - I'll do more testing when I get home.

So, now it's down to the other half of the original problem - the gnash plugin seems to burn an inordinate amount of the CPU - from 70-100% of one CPU. It no longer burns both of the CPU's at 100%, but that is probably just because there are no longer the zombie processes hanging around. Also, I had noticed on a myspace.com page (not sure if you're familiar with the typical content - it's can be an annoying site, but great for testing gnash, as it's done almost entirely in flash) - on typical pages there's a audio player that streams various selected song(s) chosen by the user that you are visiting - this flash "application" appears to be non-functional using gnash - the multi-functional button on it keeps cycling between play/pause/stop indefinitely.

Let me know if you want me to do some follow-up work on the browser repaint issue, and if you want me to create a new bug report on the 100% of CPU issue, or continue on this one.

Thanks for the great work!

-James

James Ausmus <ausmusj1>
Mon 18 Sep 2006 08:02:23 AM UTC, comment #5:

I changed the summary to better focus the problem.
Maybe we have a problem of headers incompatibility (we copy over
the mozilla-sdk headers, which might not match with your installed browser).
Since we now copied in an older set of headers, could you try again ?

Sandro Santilli <strk>
Project Member
Thu 14 Sep 2006 05:16:48 PM UTC, comment #4:

Nope, still does it, as of CVS from 2006-09-14. Neiter closing the FF tab, or closing the FF window killed either of the gnash processes. However, no processes went zombie this time, I was able to kill both of them normally, with just a kill command.

James Ausmus <ausmusj1>
Sat 09 Sep 2006 10:34:38 PM UTC, comment #3:

I think this should be fixed in current CVS (there are kill calls for each child on page leaving). Please have a test.

Sandro Santilli <strk>
Project Member
Wed 07 Jun 2006 05:30:25 PM UTC, comment #2:

One more piece of additional info.

After the above processes stayed alive, I did a killall gnash. This did close down one of the processes, but the other processes stayed alive, dropped CPU usage to 0, and became a zombie process. kill -9 <pid> wasn't successful in killing it either. Output of ps -elf after killall gnash & the kill -9 <pid>:

ps -elf |grep gnash

  1. Z ausmusj 13872 13864 0 75 0 - 0 exit 10:25 ? 00:00:00 [gnash] <defunct>
James Ausmus <ausmusj1>
Wed 07 Jun 2006 05:26:23 PM UTC, comment #1:

Additional info:

2 gnash processes stay open even after I close down Firefox, and they continue to burn 100% of both CPUs. Here is the output from ps -elf, in case it helps:

ps -elf |grep gnash

  1. R ausmusj 13758 1 97 85 0 - 32441 stext 10:13 ? 00:11:24 /usr/bin/gnash -x 46147941 /tmp/presence.swf -j 1 -k 1
  2. R ausmusj 13768 1 97 85 0 - 32361 stext 10:13 ? 00:11:10 /usr/bin/gnash -x 46149072 /tmp/presence.swf -j 1 -k 1
James Ausmus <ausmusj1>
Wed 07 Jun 2006 05:23:47 PM UTC, original submission:

Version: 0.7.1_p20060528
Firefox version: 1.5.0.4
GCC Version: 4.1.1
GLIBC Version: 2.4
AMD 64X2 system, 64-bit kernel, 64-bit userland.
Gentoo Distribution

When I install the gnash player (including plugin), then open Firefox, and then open up myspace.com, both of my CPU's immediately peg to 100%. Even after I close the myspace tab, and have verified that I have no open tabs with anything flash-related on them, my CPU usage stays at 100% for both CPUs. If I run top, I see 3 open gnash processes, one at 100% CPU usage (one proc), one at 99-100% (other proc), one at 1% usage.

Let me know if there are any other details I can provide to assist, and thanks for the effort, this is a much-needed project!

-James

James Ausmus <ausmusj1>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 100 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 5 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Tue 26 Sep 2006 01:45:07 PM UTCstrkStatusReady For Test=>Fixed
  Open/ClosedOpen=>Closed
Mon 18 Sep 2006 08:02:23 AM UTCstrkSummarygnash firefox plugin burns 100% of all CPUs=>plugin doesn't kill its childs
Sat 09 Sep 2006 10:34:38 PM UTCstrkStatusNone=>Ready For Test
Wed 07 Jun 2006 05:26:23 PM UTCausmusj1Carbon-Copy-=>Added ausmusj1

Back to the top


Powered by Savane 3.1-cleanup1