Open Bug 1661090 Opened 5 years ago Updated 4 years ago

browser and content hangs when zooming map at https://mrosd.maps.arcgis.com/apps/webappviewer/index.html

Categories

(Core :: Graphics, defect)

Unspecified
Windows 10
defect

Tracking

()

Performance Impact medium

People

(Reporter: asa, Unassigned)

References

()

Details

(Keywords: perf:responsiveness)

Basic information

Steps to Reproduce: visit https://mrosd.maps.arcgis.com/apps/webappviewer/index.html and zoom the map

Expected Results: browser and content remain responsive.

Actual Results: browser and content both hang temporarily and feel generally slow and sluggish.


More information

Profile URL: https://share.firefox.dev/2QnCa1P

Basic systems configuration:

OS version: Windows 10 (Version 10.0.18363 Build 18363)

GPU model: Intel UHD Graphics 620 (I think)

Number of cores: Intel Core i7-8650U CPU @ 1.90GHz, 2112 Mhz, 4 Cores, 8 Logical Processors

Amount of memory (RAM): 16.0 GB

I see DisplaySVGGeometry::HitTest stalled waiting for D2DFactory::CreateStrokeStyle()
I expect it's waiting for access to D2D.
https://share.firefox.dev/31uo3hI

Not sure if this is a commen resource contention?
Moving to Core::WebPainting, I believe that's the right component.

Component: Performance → Web Painting
Whiteboard: [qf]
Whiteboard: [qf] → [qf:p2:responsiveness]

The severity field is not set for this bug.
:mattwoodrow, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(matt.woodrow)

I'll move this to Graphics, since this is almost certainly D2D contention between the main thread, and the OMTP threads.

This should be fixed once WebRender is enabled.

Component: Web Painting → Graphics
Flags: needinfo?(matt.woodrow)
Severity: -- → S3
Performance Impact: --- → P2
Whiteboard: [qf:p2:responsiveness]
You need to log in before you can comment on or make changes to this bug.