windows 10 firefox does not render correctly after reopen from minimized window

RESOLVED DUPLICATE of bug 1232042

Status

()

Core
Graphics
RESOLVED DUPLICATE of bug 1232042
a year ago
a year ago

People

(Reporter: jigar shah, Unassigned)

Tracking

43 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: gfx-noted)

Attachments

(5 attachments, 1 obsolete attachment)

(Reporter)

Description

a year ago
Created attachment 8703286 [details]
Fullscreen capture 01-01-2016 194503.bmp

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151223140742

Steps to reproduce:

windows 10 yoga 3 pro - i right click and it shows black patch


Actual results:

shows black patch-once i hover mouse it shows something


Expected results:

menu should render correctly

Comment 1

a year ago
Can you upload the attachment again? it seems be corrupted on the server, see also bug 1236161.
Flags: needinfo?(bugmail)
Attachment #8703286 - Attachment mime type: image/png → image/bmp
Component: Untriaged → Menus
(Reporter)

Comment 2

a year ago
Created attachment 8703335 [details]
Address bar and menubar also not painted correctly

Its not only context menu...regular windows also not painted correctly. no issue with other browsers or app
Flags: needinfo?(bugmail)
(Reporter)

Updated

a year ago
Summary: windows 10 context menu does not paint → windows 10 firefox does not render correctly after reopen from minimized window
(Reporter)

Comment 3

a year ago
Created attachment 8703336 [details]
After 'show desktop' minimize...reopened and it showsup like above

Updated

a year ago
Component: Menus → Graphics
Product: Firefox → Core

Comment 4

a year ago
Can you reproduce this in safe mode?

Can you go to about:support (Help > troubleshooting information) and copy-paste the "grahpics" section into a comment here?
Flags: needinfo?(bugmail)
(Reporter)

Comment 5

a year ago
Created attachment 8706610 [details]
safemode graphics info
Flags: needinfo?(bugmail)
(Reporter)

Comment 6

a year ago
Created attachment 8706613 [details]
fresh profile reproduced
(Reporter)

Comment 7

a year ago
Created attachment 8706615 [details]
fresh profile graphics info

Comment 8

a year ago
(In reply to jigar shah from comment #5)
> Created attachment 8706610 [details]
> safemode graphics info

But did you reproduce the issue in safe mode, or did it go away in safe mode?

Milan, this looks like a relatively up-to-date Intel driver, but with a large screen (3200px wide). Known issue?
Flags: needinfo?(milan)
Flags: needinfo?(bugmail)
Attachment #8703286 - Attachment is obsolete: true
Bas, can you reproduce?  And, yes, having the information on whether the safe mode "saves" us is critical here.
Flags: needinfo?(milan) → needinfo?(bas)
(In reply to Milan Sreckovic [:milan] from comment #9)
> Bas, can you reproduce?  And, yes, having the information on whether the
> safe mode "saves" us is critical here.

I don't see any artifacts like this, I don't have HD graphics 5300 to try and reproduce either though.
Flags: needinfo?(bas)
(Reporter)

Comment 11

a year ago
Safe mode its not reproducible. With fresh profile it is.
Flags: needinfo?(bugmail)
Jeff, do we have (or can we get) this hardware in Toronto?
Flags: needinfo?(jmuizelaar)
Whiteboard: gfx-noted
I have similar issues on my system. Happy to lend my system to the cause if more info is needed.
I'm on a 4K monitor as well.
Possibly a duplicate of bug 1232042; I understand the patches on that bug are not quite right, but if you can try a build with those and let us know if the problem goes away, it'll help.
Flags: needinfo?(jmuizelaar) → needinfo?(ryanvm)
I've been running with the patch from bug 1232042 applied locally for the last day and haven't had a single invalidation issue when restoring from minimized since. I've been trying to minimize more than usual too in an effort to hit the bug.
Flags: needinfo?(ryanvm)
Let's call it a duplicate of 1232042.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1232042
You need to log in before you can comment on or make changes to this bug.