New issue
Advanced search Search tips

Issue 768208 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
rbyers@chromium.org
nyerramilli@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Sites gets crashed on Chrome 61 version, But works fine on it's other versions. Also works fine 62 beta version. No Issues on other browsers.

Reported by ravish...@gmail.com, Sep 24 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.29 Safari/537.36

Steps to reproduce the problem:
1. It is not not on all the sites.
2. I am using my company web site https://omnidesk.newgen.co.in
3. Can't share credentials

What is the expected behavior?
It should response properly. Suddenly site goes on hang state and after some time again works properly. and things go repetitively like this.

What went wrong?
Site suddenly goes on hang state and after some time again works properly. and things go repetitively like this.

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes Working on both 60 and 62 beta version.

Chrome version: 61.0.5136  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Site also working fine with other browsers. Please help immediately. you can contact me @ +91-9711139977

Comment 1 by phistuck@gmail.com, Sep 24 2017 

Since an account cannot be created, it will be harder to identify the issue.
Do you see those crashes listed in chrome://crashes perhaps? If so, please, comment here with the crash IDs of those crashes.

If you want to expedite the resolution, you can use the bisect tool (it only requires Python) -
https://www.chromium.org/developers/bisect-builds-py
This is the Python script -
https://chromium.googlesource.com/chromium/src/+/master/tools/bisect-builds.py

That will identify the approximate time where (a) the crash started occurring and (b) stopped occurring (you need to run it twice).

Comment 2 by nyerramilli@chromium.org, Sep 25 2017

Labels: Needs-Triage-M61 Needs-Feedback

Comment 3 by ravish...@gmail.com, Sep 25 2017 

Crash ID: ebe61306-9486-4f29-832b-9722420daff5
Crash ID: 6e868d26-619b-4366-97bc-8c6d5fda1223


Kindly check if you get any help from this..
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 25 2017

Cc: nyerramilli@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "nyerramilli@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by pbomm...@chromium.org, Sep 25 2017 

 ravishd82@ can you please provide report_id from Chrome://crashes, Also without any login credentials it's hard for us to know what went wrong.

Comment 6 by rbyers@chromium.org, Sep 25 2017

Cc: rbyers@chromium.org
Really what we need to do is bisect, but without access to the site that's impossible for us to do.

ravishd82@ are you a developer?  Any chance you could follow the instructions at https://www.chromium.org/developers/bisect-builds-py in order to bisect chromium builds yourself?  Unfortunately we don't have a complete build archive available publicly, but the above steps should at least give us a rough range of what change may have broken this site.

Comment 7 by ravish...@gmail.com, Sep 28 2017 

I can share you remote session if you can provide time according to IST..
This will help to see the actual issue...

Kindly suggest..

Comment 8 by ravish...@gmail.com, Sep 29 2017 

Gentle Reminder.

Comment 9 by kkaluri@chromium.org, Nov 1 2017

Labels: Needs-Feedback
Gentle Ping.....

rbyers@ the reporter has responded to your query in comment #7, Could you please look into it.

Comment 10 by rbyers@chromium.org, Nov 1 2017 

Sorry for the delay.  Chrome 62 is now in stable and rolled out to all users, so at this point Chrome 61 would not get a fix for this.  It's working fine in 62, right?

If you'd still like to investigate, than can you please paste in some crash IDs from chrome://crashes?  The strings in #3 are not valid crash IDs, they should look something like "b5e0c1ad7eaacdf8".

Comment 11 by dtapu...@chromium.org, Feb 8 2018

Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.
►

Sign in to add a comment