Bug 3244 - High processor used during flash video
Summary: High processor used during flash video
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-11-01 15:43 CET by Arnaud Vacquier
Modified: 2012-03-10 16:01 CET (History)
2 users (show)

See Also:
Source RPM: flash-player-plugin
CVE:
Status comment:

Attachments
processor run 78% (283.28 KB, image/png)
2011-11-01 15:44 CET, Arnaud Vacquier 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Arnaud Vacquier 2011-11-01 15:43:53 CET 
Description of problem:
When i watch video on the web, the processor is use 78-84%

Version-Release number of selected component (if applicable):
Gnome 2
Chromium 14.0.835.163
Flash-player-plugin 11.0.1.152-1.mga1.nonfree
Comment 1 Arnaud Vacquier 2011-11-01 15:44:59 CET 
Created attachment 1034 [details]
processor run 78%
Comment 2 Manuel Hiebel 2011-11-07 02:01:42 CET 
You should report this bug at adobe...

Keywords: (none) => Triaged
Source RPM: (none) => flash-player-plugin

Manuel Hiebel 2011-11-14 00:36:03 CET

Keywords: Triaged => (none)

Comment 3 Marja Van Waes 2012-01-10 13:06:30 CET 
@ Arnaud

We have version 11.1.102.55-1.mga1.nonfree now, do you still have this problem?

If so, can you please give a link to your upstream report?

cc'ing maintainer

CC: (none) => anssi.hannula, marja11

Comment 4 Marja Van Waes 2012-02-22 12:50:16 CET 
(In reply to comment #3)
> @ Arnaud
> 
> We have version 11.1.102.55-1.mga1.nonfree now, do you still have this problem?
> 
> If so, can you please give a link to your upstream report?
> 
> cc'ing maintainer

@ and again a newer version: 11.1.102.62-1.mga1.nonfree

Please reply to the above question , Arnaud, to avoid this bug being closed as OLD.

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2012-03-10 16:01:41 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.