Open
Bug 1296970
Opened 9 years ago
Updated 3 years ago
Corrupted rendering on Intel(R) HD Graphics 520 V 20.19.15.4380 (2-2-2016)
Categories
(Core :: Graphics: Layers, defect)
Core
Graphics: Layers
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| platform-rel | --- | - |
People
(Reporter: BenWa, Unassigned)
Details
(Whiteboard: [platform-rel-Intel])
Attachments
(1 file)
|
1.66 KB,
text/plain
|
Details |
Updated•9 years ago
|
platform-rel: --- → ?
Whiteboard: [platform-rel-Intel]
Updated•9 years ago
|
platform-rel: ? → +
Updated•9 years ago
|
platform-rel: + → -
Comment 1•9 years ago
|
||
On a HP EliteBook 840 G3 with HD Graphics 520 embedded in i5-6300U, Intel driver 20.19.15.4377 (1-25-2016) causes graphics glitches (black rectangles when scrolling and failure to repaint the content area immediately when switching tabs; black rectangles also spread to browser chrome occasionally) and crashes (the driver crashes often and sometimes takes Firefox with it.)
This is with Windows 7 Enterprise and Firefox ESR 45.8.0. (This is another person's enterprise-managed laptop, so I'm not at liberty to test with different Firefox or driver versions. I expect the enterprise admin to upgrade the driver before pushing ESR 52.)
Sample crash reports:
https://crash-stats.mozilla.com/report/index/54f2b180-c7cb-459a-8fd8-61d0a2170406
https://crash-stats.mozilla.com/report/index/f0a7314a-c5df-4976-a03c-9ac8b2170406
https://crash-stats.mozilla.com/report/index/d78be317-c18f-4e37-a001-25cee2170406
Since there exist a newer driver for HD Graphics 520 (from two weeks ago), I wonder if it made sense to just blocklist driver 4380 and older for HD Graphics 520. Do we have the capability of blocklisting on a per GPU model basis without having to blocklist Intel drivers of the same vintage for e.g. HD Graphics 4000, which doesn't exhibit these problems?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•