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

Issue 649680 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

crash when closing new tab or pop-up from Saba Enterprise 5.5.2.1

Reported by malay...@gmail.com, Sep 23 2016

Issue description

Chrome Version       : 53.0.2785.116 (win7 and Win10 both reproduce)
URLs (if applicable) : https://lmgr.bai.org
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: N/A
    Firefox: OK 47.0.1
         IE: OK 11.187.14393.0


What steps will reproduce the problem?
(1) Log in and Open any SCORM training course, which creates a new tab. The undelying application is Saba Enterprise 5.5.2.1, a market-leading enterprise training app
(2) Finish the scorm course, which results in closing of the new tab
(3) 

What is the expected result?
Windows close without error, user is redirected to results page

What happens instead?
See two Aw snap, both in the base page and in a communication pop-up generated by the application which normally says "please wait while we save your results"). The pop-up has a URL of about:blank which is incorrect.

Please provide any additional information below. Attach a screenshot if
possible.

This did not happen in any version of Chrome 52.x. First encountered on 2016-09-23 by our testers, now being reported by hundreds of customers.

Crash dump attached. Login details for the application can be provided for reproduction (unsure how to reduce test case further)
 
6cce6b3e-44d1-41e5-8073-837af9ef6a61.dmp
627 KB Download

Comment 1 by malay...@gmail.com, Sep 23 2016

Same issue is reproducible with Chrome 53 on Mac OSX; see this crash bug report made by a Mac user:
https://bugs.chromium.org/p/chromium/issues/detail?id=649706

Comment 2 by malay...@gmail.com, Sep 26 2016

Additional information: I am not seeing this same crash on beta or canary versions. Only v53 seems to be bad.

OS Windows 10 Enterprise, Version 1607, Build 14393.187
No Crash: Chrome 32-bit stable Version 52.x (unable to retrieve old version info)
CRASHES: Chrome 32-bit stable 53.0.2785.116 m
No Crash: Chrome 32-bit Beta Version 54.0.2840.34 beta-m
No Crash: Version 55.0.2872.0 canary (64-bit)

We have hundreds of thousands of users complaining about this crash in the interim however. I will look at the changelog for 54 to see if there is anything obvious that might have "fixed" things.
Labels: Needs-Bisect
Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
@malayter: Could you please provide us the sample credentials to triage this issue further.

Thank you.
Screen Shot 2016-09-28 at 2.38.24 PM.png
409 KB View Download

Comment 5 by malay...@gmail.com, Oct 4 2016

Update: This crash is still present in recently released stable version 53.0.2785.143, but appears fixed in recent beta update 54.0.2840.41 beta-m. TEsted on Windows and Mac desktop versions.

@rnimmagadda Will provide login credentials and repro steps in direct email 


Status: WontFix (was: Unconfirmed)
Thanks for  the upgrade, closing as per #5.

Comment 7 by malay...@gmail.com, Feb 10 2017

This crash re-appeared in Chrome 56.0.2924.87, and is still present in 57.0.2987.37 beta on Windows 10.
We really need help on this one; we have no idea what is causing the crash. We could even change our app to work around it if we knew the root cause. Affection hundreds of thousands of our customers.

Not present in current versions of IE, Edge, or Firefox as of this date.

Should I open a new bug? I submitted a crash report from within chrome for this issue. Is it possible for me to see that?

Comment 8 by malay...@gmail.com, Feb 10 2017

New issue created with recent crash report, https://bugs.chromium.org/p/chromium/issues/detail?id=691012

Sign in to add a comment