App crashes on launching chrome from Multitasking mode to normal mode in sign in screen. |
||||||||||
Issue descriptionApp Version: 59.0.3054.0 canary iOS Version: 9.3.5,iOS 10 Device : iPad Air2, iPad Pro,iPad Mini Steps to reproduce: 1. Launch chrome in normal mode. 2. Goto Bookmarks and send the app to background. 3. Launch safari or any other app. 4. Launch chrome in Multitasking mode. 5. Tap on “Sign in” in bookmarks > Tap on “Email or phone”. 6. Tap on Enter twice. 7. Send the app to background. 8. Relaunch chrome in normal mode. Observed results: App crashes Expected results: App should not crash Number of times you were able to reproduce: 3/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: NA Bug reproducible on Dolphin/Safari/Firefox: Safari : NA Bug reproducible on current stable build (App Version, iOS Version): Yes in M57 Bug reproducible on the current beta channel build (App Version, iOS Version): Yes in M58 Link to Video : https://drive.google.com/a/google.com/file/d/0B-tbaGTQZtpQdjRMc0dVM1ZtTzg/view?usp=sharing Crash log: https://crash.corp.google.com/browse?stbtiq=c81c257d60000000 Stack trace : Thread 0 CRASHED [EXC_SOFTWARE / UNCAUGHT_NS_EXCEPTION @ 0x000000018f4451b8 ] MAGIC SIGNATURE THREAD Stack Quality80%Show frame trust levels 0x000000018f4451b8 (CoreFoundation + 0x001301b8 ) __exceptionPreprocess 0x000000018de7c558 (libobjc.A.dylib + 0x00008558 ) objc_exception_throw 0x000000018f445088 (CoreFoundation + 0x00130088 ) +[NSException raise:format:arguments:] 0x000000018fefd094 (Foundation + 0x000ae094 ) -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] 0x00000001955d3494 (UIKit + 0x002ef494 ) UIViewReportBrokenSuperviewChain 0x00000001955d3b50 (UIKit + 0x002efb50 ) _UIViewTopDownSubtreeTraversal 0x0000000195665290 (UIKit + 0x00381290 ) -[UIViewController _setPresentationController:] 0x000000019565ea04 (UIKit + 0x0037aa04 ) -[UIViewController _adaptedPresentationControllerForTraitCollection:withTransitionCoordinator:] 0x00000001956464fc (UIKit + 0x003624fc ) -[UIPresentationController _sharedParent:willTransitionToTraitCollection:withTransitionCoordinator:] 0x000000019564638c (UIKit + 0x0036238c ) -[UIPresentationController _window:willTransitionToTraitCollection:withTransitionCoordinator:] 0x00000001956552f8 (UIKit + 0x003712f8 ) -[UIViewController _window:willTransitionToTraitCollection:withTransitionCoordinator:] 0x00000001956463b8 (UIKit + 0x003623b8 ) -[UIPresentationController _window:willTransitionToTraitCollection:withTransitionCoordinator:] 0x00000001956552f8 (UIKit + 0x003712f8 ) -[UIViewController _window:willTransitionToTraitCollection:withTransitionCoordinator:] 0x00000001955cd9d8 (UIKit + 0x002e99d8 ) -[UIWindow _willTransitionToTraitCollection:withTransitionCoordinator:] 0x00000001955cd680 (UIKit + 0x002e9680 ) -[UIWindow _willChangeToSize:orientation:screen:withTransitionCoordinator:] 0x00000001955c8ed0 (UIKit + 0x002e4ed0 ) -[UIWindow _rotateToBounds:withAnimator:transitionContext:] 0x00000001955ca804 (UIKit + 0x002e6804 ) -[UIWindow _rotateWindowToOrientation:updateStatusBar:duration:skipCallbacks:] 0x0000000195372cb8 (UIKit + 0x0008ecb8 ) -[UIWindow _setRotatableClient:toOrientation:updateStatusBar:duration:force:isRotating:] 0x0000000195372944 (UIKit + 0x0008e944 ) -[UIWindow _setRotatableViewOrientation:updateStatusBar:duration:force:] 0x0000000195369474 (UIKit + 0x00085474 ) __57-[UIWindow _updateToInterfaceOrientation:duration:force:]_block_invoke 0x00000001952f4b24 (UIKit + 0x00010b24 ) -[UIWindow _updateToInterfaceOrientation:duration:force:] 0x00000001957b939c (UIKit + 0x004d539c ) -[UIScreen _notifySceneBoundsChanged:] 0x00000001957b70e0 (UIKit + 0x004d30e0 ) -[UIScreen _updateReferenceBoundsToSceneReferenceBounds:fromInterfaceOrientation:animated:] 0x0000000195584d64 (UIKit + 0x002a0d64 ) __83-[UIApplication _createSnapshotContextForScene:withName:performLayoutWithSettings:]_block_invoke_2 0x000000019565c634 (UIKit + 0x00378634 ) +[UIViewController _performWithoutDeferringTransitions:] 0x0000000195584d0c (UIKit + 0x002a0d0c ) __83-[UIApplication _createSnapshotContextForScene:withName:performLayoutWithSettings:]_block_invoke 0x00000001953017d8 (UIKit + 0x0001d7d8 ) +[UIView(Animation) performWithoutAnimation:] 0x00000001955849d4 (UIKit + 0x002a09d4 ) -[UIApplication _createSnapshotContextForScene:withName:performLayoutWithSettings:] 0x0000000195585f9c (UIKit + 0x002a1f9c ) __65-[UIApplication _performSnapshotsWithAction:forScene:completion:]_block_invoke_2 0x0000000191019858 (FrontBoardServices + 0x00038858 ) -[FBSSceneSnapshotAction _executeNextRequest] 0x000000019101947c (FrontBoardServices + 0x0003847c ) -[FBSSceneSnapshotAction executeRequestsWithHandler:completionHandler:expirationHandler:] 0x0000000195585ebc (UIKit + 0x002a1ebc ) __65-[UIApplication _performSnapshotsWithAction:forScene:completion:]_block_invoke 0x0000000195585524 (UIKit + 0x002a1524 ) -[UIApplication _beginSnapshotSessionForScene:withSnapshotBlock:] 0x0000000195585d48 (UIKit + 0x002a1d48 ) -[UIApplication _performSnapshotsWithAction:forScene:completion:] 0x0000000195585aa4 (UIKit + 0x002a1aa4 ) -[UIApplication _handleSnapshotAction:forScene:completion:] 0x0000000195581df8 (UIKit + 0x0029ddf8 ) __102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke.2114 0x0000000195581900 (UIKit + 0x0029d900 ) __102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke.2100 0x0000000195584fd8 (UIKit + 0x002a0fd8 ) _runAfterCACommitDeferredBlocks 0x0000000195576d4c (UIKit + 0x00292d4c ) _cleanUpAfterCAFlushAndRunDeferredBlocks 0x00000001952e60b0 (UIKit + 0x000020b0 ) _afterCACommitHandler 0x000000018f3f20bc (CoreFoundation + 0x000dd0bc ) __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ 0x000000018f3efcec (CoreFoundation + 0x000dacec ) __CFRunLoopDoObservers 0x000000018f3f017c (CoreFoundation + 0x000db17c ) __CFRunLoopRun 0x000000018f31e2b4 (CoreFoundation + 0x000092b4 ) CFRunLoopRunSpecific 0x0000000190dd2194 (GraphicsServices + 0x0000c194 ) GSEventRunModal 0x000000019535e7f8 (UIKit + 0x0007a7f8 ) -[UIApplication _run] 0x0000000195359530 (UIKit + 0x00075530 ) UIApplicationMain 0x0000000100067004 (Chrome -chrome_exe_main.mm:63 ) main 0x000000018e3015b4 (libdyld.dylib + 0x000045b4 ) start
,
Mar 29 2017
,
Mar 29 2017
,
Mar 30 2017
Re-assigning to Jerome as he is working on iOS at the moment and I'm OOO the next 2 weeks.
,
Apr 11 2017
Users experienced this crash on the following builds: Ios Beta 58.0.3029.52 - 16.20 CPM, 1 reports, 1 clients (signature Main-Underspecified) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Apr 18 2017
My guess is, it is iOS bug. I still don't have a simple app to reproduce it. Also I can't reproduce it with iOS 9.0, but I can with iOS 10.1 and 10.2. I also noticed that click like crazy on "Sign in" button, I get: 2017-04-18 18:10:10.497 Chromium[81606:23029909] *** WebKit discarded an uncaught exception in the webView:willRemoveScrollingLayer:withContentsLayer:forNode: delegate: <NSInvalidArgumentException> -[WebActionDisablingCALayerDelegate willBeRemoved]: unrecognized selector sent to instance 0x61000000c830 (no crash nothing, and nothing for the user). This is for 10.2, even in fullscreen. Something is going on with the layers.
,
Apr 19 2017
2 taps are not necessary to reproduce this bug. This can be done with one tap on the next button if the keyboard is shown. So one tap in the textfield can replace the first tap on the button.
,
Apr 19 2017
And Chrome crash only if the panel is still displayed when the app goes in background. The following scenario will not crash: + Click Sign-in + Click twice on next button + Cancel the Sign-in dialog + Press home button to put Chrome in the background This one will also not crash: + Click Sign-in + Click twice on next button + Type an email address + Click next button + Press home button to put Chrome in the background
,
May 3 2017
jlebel@ any update on your progress?
,
May 4 2017
It looks like it is a UIKit bug. I didn't have time yet to do a simple app to reproduce it. I think this bug doesn't deserve "ReleaseBlock-Stable" since I can't reproduce it without multi-tasking, this can be reproduced only if the user stays in the email page while putting the app in background. Another way to reproduce this crash: + Open Chromium in full screen + Click on Sign-in + Click twice on next button + Switch to another app (using full screen) + Bring Chromium in multitasking
,
May 4 2017
Thanks for your explanation. I agree with you regarding the impact of this bug. Removing RBS since the number of users affected is very low and this will most likely be an external dependency.
,
May 5 2017
Users experienced this crash on the following builds: Ios Dev 60.0.3087.0 - 91.99 CPM, 1 reports, 1 clients (signature Main-Underspecified) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jun 5 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 12 2017
,
Jul 6
Crash analysis has not encountered any reports for this bug for the past 90 days. We have added the label 'crash-BugNoRepro' Crash analysis will be automatically closing the bug in 10 days. If you do not want Crash analysis to automatically close the bug, please remove the label 'crash-BugNoRepro'. If you have any feedback on this feature, please contact pranavk@
,
Jul 16
Crash analysis has not encountered any reports for this bug for the past 90 days. Hence as per the comment 10 days ago, we are closing the bug and setting the status to WontFix. If you have any feedback on this feature, please contact pranavk@ |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by sczs@chromium.org
, Mar 29 2017Components: -UI>Settings UI>Browser>Bookmarks Services>SignIn
Labels: M-59
Owner: msarda@chromium.org