Created attachment 8732475 [details] Another screenshot Just applied update and restarted, problem still exists. Tried to resize window but the problem only becomes worse as evidenced in this screenshot.
Thanks for the report. Are you able to run mozregression to find what introduced this regression? And would you be able to supply a file, scrubbed of confidential information, which can reproduce this?
(In reply to Jamie Nicol [:jnicol] from comment #2) > Thanks for the report. Are you able to run mozregression to find what > introduced this regression? And would you be able to supply a file, scrubbed > of confidential information, which can reproduce this? Possibly. This only reproduces on my home machine, and not 100% reliably so it might take some time. I'll give it a try tomorrow.
This might be a long shot, but you should also look at about:memory and check if the memory usage is particularly high. I think that one possible side effect of running low on memory is graphics stuff going weird, and we have a number of bugs on file about high memory usage with Google Sheets (such as bug 1249739).
Sounds possible although I don't remember memory usage being particularly high on that occasion. I brought my laptop to work to try and repro and run mozregression but was unable to repro. If I hit it again, I'll check memory usage.
Brought my computer to try reproducing but without any luck. I'll follow up if I manage to repro again.
Hi, I have tried to reproduce this issue on the latest Nightly (48.0a1, Build ID 20160328004018) and Aurora (47.0a2, Build ID 20160328004018) and no matter how many times I resize my window, minimize or switch tabs I can't reproduce this issue. If you figure out how to reproduce it consistently please add steps to reproduce. Thanks, Cipri
I'm closing this since the issue does not appear to be reproducible. Please reopen the bug report if the issue returns.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.