New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 851659 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Transitions in a tab that is not the topmost tab will freeze and eventually crash the tab.

Reported by steveayo...@gmail.com, Jun 11 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. https://alexmasselot.github.io/js-transition-perf/d3;n=100;refresh=1000;leap=0.25
2. Open another tab and leave the above one on the non-topmost tab.
3. It will die after a while.

What is the expected behavior?
The correct behavior is to continue with the transitions.

What went wrong?
If you let either run in a non-topmost-tab for more than about 45 minutes that tab will not recover and just has to be closed.  Shorter periods will cause the tab to freeze for a while, but will resume and continue properly.

When it dies, it goes to 'page is unresponsive', and you just have to close the tab.

Did this work before? N/A 

Does this work in other browsers? No
 Go to the link below and let it run as described.

Both the "d3" and the "SVG with CSS" will exhibit the problem.

Chrome version: 66.0.3359.181  Channel: n/a
OS Version: 10.0
Flash Version: 

Both my application and the above tab exhibit the same behavior on Windows and Chromebook devices, with at least the last 2 releases of Chrome.
 
Labels: Needs-Milestone
Cc: krajshree@chromium.org
Components: Blink>JavaScript
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome latest stable #67.0.3396.79 and latest canary #69.0.3455.0.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to https://alexmasselot.github.io/js-transition-perf/d3;n=100;refresh=1000;leap=0.25
2. Opened another tab and left the above one on the non-topmost tab.
3. Observed that it did not crash or freeze.

steveayork60@ - Could you please check the issue on latest stable #67.0.3396.79 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
Running this test url:
Version 67.0.3396.87 (Official Build) (64-bit)
No apps or extensions.
Did the 'Clean up computer', it said 'no harmful software found'.

I have submitted two dumps and referenced this entry in the text so they would get to you.  One dump is from the url i specified in here after crash and trying to load the same url, the other one is from my own application when running in the non-top tab right after it died.

Notes:
I'm not minimizing the chrome window when i run this test, but i do have other windows open on top of it while it is running.
I have not tested it with the Chrome window minimized.
Same behavior if it is the topmost window or not - only related to the topmost tab in the Chrome window.

Some better timings:
If this test app is a background tab for 15 min, when you switch to it, it will be frozern for a short time and recover.
If this test app is a background tab for 1 hour and 20 min, when you switch to it, it will be dead and 30 seconds later show the unresponsive message.

It happens 100% of the time on all my Windows boxes (Win10 and latest Chrome).

----

On a Chromebook running
Chrome ver 66.0.3359.137 (64bit)

The test app will cause it to crash in less than an hour, my app will cause it to crash in about 10 minutes.  Otherwise, same situation.

Thank you for your help here!!!
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 16 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Blink>JavaScript Blink
Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback
@Reporter: Could you please provide chrome crashes by navigate ""chrome://crashes/"" for  further triaging from our end.

Thanks.!
I have uploaded the last 4 crashes in my //crashes page.  The ids are in the attached pic.  These are from my dev box, not from test machines, so not sure if they are helpful or same issue.
crashes.png
23.4 KB View Download
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 20 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Feedback
@Reporter: Could you please share the crash ID as highlighted in the screen shot with this comment, which helps us to triage it in a better way.

Thanks!
851659.png
72.9 KB View Download
Just a moment ago, my real live app crashed (not the sample one above), and i submitted it, and specified this bug #.


Project Member

Comment 11 by sheriffbot@chromium.org, Jun 25 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
@Reporter: As per comment#10, it is understood that you have filed an other issue, it would be helpful if mentioned the issue ID so that we can dupe this into that issue.

Thanks!
I can't get back to that screen now.  The crashes are different.

My only option seems to be to simply submit the crash, and put in the comments, this bug #.

I am still trying.


Project Member

Comment 14 by sheriffbot@chromium.org, Jun 26 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 15 by kojii@chromium.org, Jun 26 2018

Labels: Needs-Feedback
Starting as of a couple of days ago, this longer crashes.  Either with the test link above, or with my real application.

The test application resumes, whereas my app is sitting at an "aw snap".

In short, i still have the problem, but the test link does not.
Project Member

Comment 17 by sheriffbot@chromium.org, Jun 26 2018

Cc: kojii@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Oops , i meant "...no longer crashes...".

:)
Here is the current situation.  In my app, if i leave it as the non-topmost-tab for 15 min, it is frozen when i switch back to it.

And then i get the Page Unresponsive error.  And my only options are wait or exit page.

Clicking F5 or refresh circle only spins and returns the same message.

How can i get this state info to you?  Its technically not a 'crash', but the browser session is not working.

Hmm, after 30 more seconds or so, i got the "aw snap".  Using this i can submit another one and reference this bug entry, but you made it sound like that is not helpful.

What can i do to get this to you?

Thanks!

Comment 20 by kojii@chromium.org, Jun 27 2018

Can you please refer to comment #9? The one you provided in #7 are "Local Crash ID". They will have "Crash Report ID" once they are uploaded.
ok got it.

Uploaded Crash Report ID 747963b6dc8fbc7b (Local Crash ID: 16da9367-31de-44fd-a994-25bdc0b7f9f6)

Thank you!

Comment 22 by kojii@chromium.org, Jun 28 2018

Components: -Blink Blink>JavaScript>GC
Mergedinto: 763361
Status: Duplicate (was: Unconfirmed)
#21: Thank you, it looks like JavaScript crashes while trying to compact memory.

v8::internal::MarkCompactCollector::ProcessMarkingWorklist()
v8::internal::MarkCompactCollector::MarkLiveObjects()
v8::internal::MarkCompactCollector::CollectGarbage()
v8::internal::Heap::MarkCompact()
v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector,v8::GCCallbackFlags)
v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace,v8::internal::GarbageCollectionReason,v8::GCCallbackFlags)
v8::internal::Heap::AllocateRawWithRetry(int,v8::internal::AllocationSpace,v8::internal::AllocationAlignment)
v8::internal::Factory::NewFillerObject(int,bool,v8::internal::AllocationSpace)
v8::internal::Runtime_AllocateInNewSpace(int,v8::internal::Object * *,v8::internal::Isolate *)

This issue is being investigated in issue 763361, though, sorry, the issue is probably not visible.

Sign in to add a comment