Closed
Bug 1300338
Opened 8 years ago
Closed 8 years ago
URL (from Google) causes hang on multiple machines and Windows 10 versions
Categories
(Core :: Graphics, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla52
People
(Reporter: dtresearch, Assigned: bas.schouten)
References
(Blocks 1 open bug, )
Details
(Keywords: hang, regression, reproducible, Whiteboard: gfx-noted)
Attachments
(1 file)
58 bytes,
text/x-review-board-request
|
jrmuizel
:
review+
gchang
:
approval-mozilla-aurora+
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160823121617
Steps to reproduce:
Go to URL https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=7&cad=rja&uact=8&ved=0ahUKEwjeh8DgzPPOAhUHyWMKHWxXDTMQFghKMAY&url=http%3A%2F%2Faperiodical.com%2F2014%2F11%2Fan-alan-turing-expert-answers-your-the-imitation-game-questions%2F&usg=AFQjCNERgGT3co3w46B3V4SrhQMsCXZqhQ
Actual results:
The address bar transitions from the Google URL to the actual URL. The page seems to load. After a few seconds the little spinner in the tab freezes. After this, any attempt to interact with Firefox results in the "Not Responding" message in the title bar. It may still be closed by right-clicking the task bar and clicking "close", which has to be done twice, or via the Task Manager. The window will still minimize and restore while in this state. On the 8 core computer the Task manager shows Firefox at 12.5-14.4% constantly, indicating 100% for the task. The two computers initially showing the problem are Windows 10 build 10586. These computers evolved independently, they are not clones. I also recreated the problem on an "almost virgin" dual-core running Windows 10 Build 14393.rs1_release_inmarket.160819-1924 and the "latest" Firefox as of August 2016. The CPU on this machine for the task is at 51-54% indicating 100% for the task. I also recreated the problem on a quad-core laptop running 10586.
Expected results:
Going to the URL with IE 11 results in the page loading and scrolling normally. It also seems to open normally on Windows 7 Ultimate build 7601, although there is a slight hiccup at the point where it would otherwise hang. There also were normal results on a "well worn" Windows XP SP3 Build 2600.xpsp_sp3_qfe.130704-0421, a dual-core desktop running Windows 7 Pro 32 bit build 7601, a dual-core laptop running Windows 10 Home build 10240, a quad-core desktop running Windows 8 Pro Build 9200, and a dual-core desktop running Windows 8.0 Pro build 9200.
Reporter | ||
Updated•8 years ago
|
![]() |
||
Comment 1•8 years ago
|
||
[Tracking Requested - why for this release]: Browser hangs
#1 With HWA, Firefox hangs.
#2 Without HWA, Fierfox does not hang. Blank page is shown, but there are invisible links.
(I will file the other new bug for #2 problem.)
#1 Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=36c1e4eb0c9141aae4071a917ce4e3a59f5a79c6&tochange=d74084d072f0b5dfb00e3fbc103bef0a3fecbf85
#1 Regressed by: Bug 1220629
Blocks: 1220629
Status: UNCONFIRMED → NEW
status-firefox48:
--- → wontfix
status-firefox49:
--- → affected
status-firefox50:
--- → affected
status-firefox51:
--- → affected
status-firefox-esr45:
--- → unaffected
tracking-firefox49:
--- → ?
tracking-firefox50:
--- → ?
tracking-firefox51:
--- → ?
Component: Untriaged → Graphics
Ever confirmed: true
Keywords: hang,
reproducible
Product: Firefox → Core
![]() |
||
Comment 2•8 years ago
|
||
> #2 Without HWA, Fierfox does not hang. Blank page is shown, but there are invisible links.
(I will file the other new bug for #2 problem.)
please ignore this.
It seems no problem without HWA
Comment 3•8 years ago
|
||
Track for 49+/50+/51+ as this is a reproducible behavior and hang issue with HWA.
Updated•8 years ago
|
Severity: minor → major
Comment 4•8 years ago
|
||
Can reproduce on current nightly. Hangs browser straight away.
Updated•8 years ago
|
Flags: needinfo?(bas)
Updated•8 years ago
|
Whiteboard: gfx-noted
Assignee | ||
Updated•8 years ago
|
Assignee | ||
Comment 5•8 years ago
|
||
In investigating this bug I've found an obvious performance optimization that as a side-effect fixes this bug. Patch upcoming.
Comment hidden (mozreview-request) |
Comment 7•8 years ago
|
||
Regression from Firefox 46, too late to fix this in 49. We can still take a patch for 50 though.
Comment 8•8 years ago
|
||
mozreview-review |
Comment on attachment 8790329 [details]
Bug 1300338: Do not attempt to preserve layer content when we're going to override it in a blend operation anyway.
https://reviewboard.mozilla.org/r/78216/#review77340
Attachment #8790329 -
Flags: review?(jmuizelaar) → review+
Pushed by bschouten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1fef8a245875
Do not attempt to preserve layer content when we're going to override it in a blend operation anyway. r=jrmuizel
I had to back this out for Windows 8 reftest failures like https://treeherder.mozilla.org/logviewer.html#?job_id=3549715&repo=autoland
https://hg.mozilla.org/integration/autoland/rev/a001e3d12ce3
Flags: needinfo?(bas)
Comment 11•8 years ago
|
||
Bulk move of gfx-noted bugs without priority to P3 for tracking.
Priority: -- → P3
Comment 12•8 years ago
|
||
Pushed by bschouten@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/13fe99de32f6
Do not attempt to preserve layer content when we're going to override it in a blend operation anyway. r=jrmuizel
Comment 13•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox52:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(bas)
Comment 14•8 years ago
|
||
Hi :bas,
Since this bug also affects 50/51, do you think the patch is worth uplifting to 50/51?
Flags: needinfo?(bas)
Assignee | ||
Comment 15•8 years ago
|
||
(In reply to Gerry Chang [:gchang] from comment #14)
> Hi :bas,
> Since this bug also affects 50/51, do you think the patch is worth uplifting
> to 50/51?
50, yes, 51, it depends a little bit. The patch is not entirely risk free. It could potentially cause some graphics artifacts although so far it seems it doesn't.
Flags: needinfo?(bas)
Hello David, could you please verify this issue is fixed as expected on a latest Nightly build? Thanks!
Flags: needinfo?(dtresearch)
Reporter | ||
Comment 17•8 years ago
|
||
What is the "latest Nightly build" and where do I get it?
After many years in mainframe DP, this is my first exposure to open source.
Thanks for all the work.
I immediately turned off hardware acceleration on all my computers as soon as I became aware of it.
Comment 18•8 years ago
|
||
It's the build of Firefox which contains the most recent changes (as of the previous night). You can download it from https://nightly.mozilla.org/
Hi Bas, based on comment 15, I assume you want this wontfix'd for 50. Or are you more comfortable uplifting now that this has been in Nightly for a few weeks?
Flags: needinfo?(bas)
Comment 20•8 years ago
|
||
Hi :milan,
Can you help create a uplift request for 51 aurora?
Flags: needinfo?(milan)
Assignee | ||
Comment 21•8 years ago
|
||
Comment on attachment 8790329 [details]
Bug 1300338: Do not attempt to preserve layer content when we're going to override it in a blend operation anyway.
Approval Request Comment
[Feature/regressing bug #]: 1220629
[User impact if declined]: A website doing some very specific actions may take a very long time to complete (hang)
[Describe test coverage new/current, TreeHerder]: Extensive nightly testing
[Risks and why]: Somewhat, this could cause some artifacts with complex blending.
[String/UUID change made/needed]: None
Given the risk associated with this uplift and the fact that we are entering RC mode on Monday, this is now a wontfix for 50.
Comment 23•8 years ago
|
||
Comment on attachment 8790329 [details]
Bug 1300338: Do not attempt to preserve layer content when we're going to override it in a blend operation anyway.
Fix a hang issue. Take it in 51 aurora.
Attachment #8790329 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 24•8 years ago
|
||
bugherder uplift |
Updated•6 years ago
|
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•