Closed
Bug 1082929
Opened 11 years ago
Closed 11 years ago
[OMTC] 100% kernel CPU usage while dragging OpenStreetMap/GoogleMapsClassic
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: piotr.jerzy.jurkiewicz, Unassigned)
References
Details
(Whiteboard: [fixed by bug 1060588])
Attachments
(1 file)
65.06 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141011015303
Steps to reproduce:
Go to http://www.openstreetmap.org or https://www.google.com/maps?output=classic.
Drag a map.
Actual results:
Starting with version 33 on Windows 7, the CPU usage is very high while dragging a map. On my i5-3570k it fully uses 2/4 CPU cores! 95% of this load is kernel time.
Moreover, dragging is VERY sluggish and feels unresponsive, comparing to Firefox 32.
This is my graphics support information:
"graphics": {
"numTotalWindows": 1,
"numAcceleratedWindows": 1,
"windowLayerManagerType": "Direct3D 11",
"windowLayerManagerRemote": true,
"adapterDescription": "Intel(R) HD Graphics 4000",
"adapterVendorID": "0x8086",
"adapterDeviceID": "0x0162",
"adapterRAM": "Unknown",
"adapterDrivers": "igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32",
"driverVersion": "10.18.10.3412",
"driverDate": "1-29-2014",
"adapterDescription2": "",
"adapterVendorID2": "",
"adapterDeviceID2": "",
"adapterRAM2": "",
"adapterDrivers2": "",
"driverVersion2": "",
"driverDate2": "",
"isGPU2Active": false,
"direct2DEnabled": true,
"directWriteEnabled": true,
"directWriteVersion": "6.2.9200.16571",
"webglRenderer": "Google Inc. -- ANGLE (Intel(R) HD Graphics 4000 Direct3D9Ex vs_3_0 ps_3_0)",
"info": {
"AzureCanvasBackend": "direct2d",
"AzureSkiaAccelerated": 0,
"AzureFallbackCanvasBackend": "cairo",
"AzureContentBackend": "direct2d"
}
}
Reporter | ||
Comment 1•11 years ago
|
||
Moreover, I have discovered a very interesting thing. If you hide the left panel on Google Maps Classic (see attached screenshot), kernel CPU overload disappear and dragging is blazingly fast now. I think that it can be an useful trace for hunting this bug.
I have not discovered such a workaround for OpenStreetMap yet.
![]() |
||
Comment 2•11 years ago
|
||
Could you test with Nightly36.0a1 ( https://nightly.mozilla.org/ ) ?
Flags: needinfo?(piotr.jerzy.jurkiewicz)
Reporter | ||
Comment 3•11 years ago
|
||
On Nightly 36.0a1 the problem is gone.
Flags: needinfo?(piotr.jerzy.jurkiewicz)
![]() |
||
Comment 4•11 years ago
|
||
Regression window(m-i)
Good:
https://hg.mozilla.org/integration/mozilla-inbound/rev/bb8fc1380b00
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 ID:20140519202628
Bad:
https://hg.mozilla.org/integration/mozilla-inbound/rev/46d9ffb97fe3
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 ID:20140519224628
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=bb8fc1380b00&tochange=46d9ffb97fe3
Regressed by:
46d9ffb97fe3 Bas Schouten — Bug 899785: Switch on OMTC and async video on windows. r=BenWa
Progression window(m-i)
Bad:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2badc0f1f829
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 ID:20140914114608
Fixed:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8e28464849fa
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 ID:20140914145408
Progression pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=2badc0f1f829&tochange=8e28464849fa
Fixed by:
7861be6bf039 Bas Schouten — Bug 1060588: Use PushClipRect when possible in ClipToRegionInternal. r=jrmuizel
Blocks: 899785
Status: UNCONFIRMED → NEW
status-firefox33:
--- → affected
status-firefox34:
--- → affected
status-firefox35:
--- → fixed
status-firefox36:
--- → fixed
tracking-firefox34:
--- → ?
Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core
Summary: 100% kernel CPU usage while dragging OpenStreetMap/GoogleMapsClassic → [OMTC] 100% kernel CPU usage while dragging OpenStreetMap/GoogleMapsClassic
Whiteboard: [fixed by bug 1060588]
Updated•11 years ago
|
Flags: needinfo?(jmuizelaar)
Updated•11 years ago
|
Comment 5•11 years ago
|
||
First attempt to fix this is by uplifting the patch in bug 1060588, which now has beta approval.
Comment 6•11 years ago
|
||
Does this issue still reproduce with Firefox 34 beta2 or later?
Flags: needinfo?(piotr.jerzy.jurkiewicz)
Reporter | ||
Comment 7•11 years ago
|
||
I have tested 34 beta 4. This issue does not occur.
Flags: needinfo?(piotr.jerzy.jurkiewicz)
Comment 8•11 years ago
|
||
(In reply to Piotr Jurkiewicz from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101
> Firefox/33.0
> Build ID: 20141011015303
>
> Steps to reproduce:
>
> Go to http://www.openstreetmap.org or
> https://www.google.com/maps?output=classic.
>
> Drag a map.
>
>
> Actual results:
>
> Starting with version 33 on Windows 7, the CPU usage is very high while
> dragging a map. On my i5-3570k it fully uses 2/4 CPU cores! 95% of this load
> is kernel time.
>
> Moreover, dragging is VERY sluggish and feels unresponsive, comparing to
> Firefox 32.
>
> This is my graphics support information:
>
> "graphics": {
> "numTotalWindows": 1,
> "numAcceleratedWindows": 1,
> "windowLayerManagerType": "Direct3D 11",
> "windowLayerManagerRemote": true,
> "adapterDescription": "Intel(R) HD Graphics 4000",
> "adapterVendorID": "0x8086",
> "adapterDeviceID": "0x0162",
> "adapterRAM": "Unknown",
> "adapterDrivers": "igdumdim64 igd10iumd64 igd10iumd64 igdumdim32
> igd10iumd32 igd10iumd32",
> "driverVersion": "10.18.10.3412",
> "driverDate": "1-29-2014",
> "adapterDescription2": "",
> "adapterVendorID2": "",
> "adapterDeviceID2": "",
> "adapterRAM2": "",
> "adapterDrivers2": "",
> "driverVersion2": "",
> "driverDate2": "",
> "isGPU2Active": false,
> "direct2DEnabled": true,
> "directWriteEnabled": true,
> "directWriteVersion": "6.2.9200.16571",
> "webglRenderer": "Google Inc. -- ANGLE (Intel(R) HD Graphics 4000
> Direct3D9Ex vs_3_0 ps_3_0)",
> "info": {
> "AzureCanvasBackend": "direct2d",
> "AzureSkiaAccelerated": 0,
> "AzureFallbackCanvasBackend": "cairo",
> "AzureContentBackend": "direct2d"
> }
> }
Try bumping driver up to 10.18.10.3958.
Comment 9•11 years ago
|
||
Thank you for checking Piotr.
Resolving as fixed based on comment 7.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jmuizelaar)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•