Closed Bug 637958 Opened 14 years ago Closed 12 years ago

post b12 builds seem to consume lots of memory and cpu displaying flash

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sayrer, Unassigned)

Details

(Keywords: qawanted)

I noticed this yesterday playing youtube, Comedy Central, etc. I'm worried that this is a big regression. It was a noticeable delay in the UI, with lots of CPU being chewed up by the plugin process and the browser process. Memory usage in both was significantly higher than I remember as well.
blocking2.0: --- → ?
Hmm, post-beta-12? That rules out bug 626602. Need regression range, but better still, a profile.
i am using the latest nightly and latest flash and have no problems with high memory or CPU.. as a matter of fact it got better after b12 before that i had this problem.
(In reply to comment #1) > Hmm, post-beta-12? That rules out bug 626602. > > Need regression range, but better still, a profile. OK, I will check it out. I think I was doing ok with a circa 2/20 build, but really badly since. But I will have to check the regression range again. My perception could be wrong, since my builds haven't been as up to date as I would expect.
We're currently in a situation where if the Flash plugin is scrolled partially out of view, we are very slow. So you might want to see if that's what's happening.
Are you seeing the problems on mac? (Not sure if you set "Platform" intentionally.) Bug 626602 didn't affect mac, but mattwoodrow landed some stuff around that time that might have.
Please post some details. What site what video for how long do I have to watch the video to change what increase in memory use. I am watching a 5 minutes youtube video and I don't see any significant change in memory (~ 200MB for FF with 2 windows + youtube, 95MB for the plugin process).
Rob will try to get some more data and renominate once he does; agree that it's concerning. Roc/Mattw: can you also try to poke at this? Something we should investigate before shipping. Adding qawanted, as well.
blocking2.0: ? → ---
Keywords: qawanted
http://english.aljazeera.net/watch_now/ Mozilla/5.0 (Windows NT 6.0; rv:2.0b13pre) Gecko/20110302 Firefox/4.0b13pre Flash version: 10.2.152.26 . Somewhat anecdotal / imprecise, but, with the above Minefield build. (And I realize this is originally about Windows, and can't find the other bug I put comments on, oops. Sorry about that.) Regarding Flash CPU use - the live video player in the link above consistently uses somewhere between 63 and ~ 75% CPU while the video is playing.
CPU use is about the same with Opera 11.01 for Windows and the URL from Comment 8. ~ 60-70 % total while the video is playing. Maybe more of a Flash 10.2 issue? Subjectively seems to 'play more smoothly' with Opera 11.01 .
I am using Latest Nightly on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20130111 Firefox/21.0 (20130111030906). Using URL from Comment 8 CPU use about 26-32% depends on number of threads used. System Memory: Free: 51MB Wired: 555MB Active: 741MB Inactive: 706MB MAC config: Processor 2Ghz Intel Core 2 Duo. Memory 2GB 1067 Mhz DDR 3.
Let's call this WFM then, that's a reasonable amount of CPU in most cases.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.