New issue
Advanced search Search tips

Issue 657688 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: 2016-10-27
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Failed to execute 'insertBefore' on 'Node' error in random after Chrome v54 upgrade

Reported by pingar....@gmail.com, Oct 20 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36

Steps to reproduce the problem:
Not able to produce steps as the error happens randomly. Eg. A click on a button to do something works in the first or second times but failed in the third time.

What is the expected behavior?

What went wrong?
This is a web application developed in-house, the UI part of the application was built with ReactJS0.13. I use Chrome for my development. Everything was working find until the Chrome upgraded to ver54 on my computer.

The application crashes on random click/function. Same error as attached keep coming out every time it crashes. Everything working fine again when check on Chrome version 53.

Did this work before? Yes Chrome version 53

Chrome version: 54.0.2840.59  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 23.0 r0

Please let me know if you want to access our public facing application.
Screen Shot 2016-10-20 at 3.44.10 PM.png
279 KB View Download

Comment 1 by chrishtr@chromium.org, Oct 20 2016

Cc: chrishtr@chromium.org
Labels: Needs-Feedback
NextAction: 2016-10-27
Hello,

To investigate this bug further we will need a URL and reproduction steps on the
site.

Comment 2 by chrishtr@chromium.org, Oct 20 2016

Components: -Blink Blink>DOM

Comment 3 by chrishtr@chromium.org, Oct 20 2016

Labels: M-54

Comment 4 by pingar....@gmail.com, Oct 20 2016 

Thank you, can I send it to you at chrishtr@chromium.org

Comment 5 by chrishtr@chromium.org, Oct 20 2016 

Ok sure.

Comment 6 by pingar....@gmail.com, Oct 21 2016 

Email sent. Thank you.

Comment 7 by chrishtr@chromium.org, Oct 21 2016 

I was unable to reproduce on Chrome version 54.0.2840.71 on Linux or Mac
by following the instructions I received over email, even when repeating many
times.

Comment 8 Deleted

Comment 9 by pingar....@gmail.com, Oct 24 2016 

Chrome auto updated to batch 71 (54.0.2840.71) from 59 (54.0.2840.59 the problematic one). Unable to reproduce the issue on the new batch for some reason.

Comment 10 by tkent@chromium.org, Oct 28 2016

Status: WontFix (was: Unconfirmed)
Closing according to Comment 7 and Comment 9.

Comment 11 by chrishtr@chromium.org, Oct 31 2016 

Responding to comment 8: I did open the inspector, and saw no errors.

Glad it seems to be fixed. Please comment or open a new bug if it recurs.
►

Sign in to add a comment