Open
Bug 844251
Opened 12 years ago
Updated 2 years ago
Avoid using system wide GDI Lock causing large hangs
Categories
(Core :: Graphics, defect)
Tracking
()
NEW
People
(Reporter: BenWa, Unassigned)
Details
(Whiteboard: [Snappy])
From what I gather the GDI Lock is a system wide lock and thus it's performance is similar to main thread IO, it can block for some unbounded amount of time which is not proportional to drawing complexity. Here's a bit of information on this I found: http://www.passmark.com/support/performancetest/2d_windows7_performance.htm http://blogs.msdn.com/b/e7/archive/2009/04/25/engineering-windows-7-for-graphics-performance.aspx
Reporter | ||
Comment 1•12 years ago
|
||
It would be nice if someone can find steps to reproduce this. I imagine however that breaking on NtGdiDdDDILock (in wgdi32.pdb) might be sufficient to debug this. Perhaps we can find a way to avoid calling this on windows 7 as suggest by the msdn.com link above.
Whiteboard: [Snappy]
![]() |
||
Comment 2•10 years ago
|
||
I can reproduce the NtGdiDdDDILock problem on windows7 See https://bugzilla.mozilla.org/show_bug.cgi?id=1087827
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•