Same issue reported in Messaging now. Kindly check. 

Occurrence Process: Use device normally >> Browse internet , download contents >> Go to Message >> Read/send any message >> Press back key >> Observe


Problem : Force Close

Deleted: msg_crash.txt 3.2 KB

msg_crash.txt 3.2 KB View Download

This typically indicates that WebView is being updated. Do the crashes persist after webview is fully updated?

Tentatively closing this because the dates seem about right for the M60 release. You can expect spikes in crashes like this each time we release Chrome/WebView (roughly every 6 weeks). Please ping this bug if you see otherwise.

This shouldn't be being caused by updates - the WebView has already been loaded at this point. This would mean that the Resources object associated with the current Context doesn't have the WebView resources loaded into it.

This means the app has done something it shouldn't with its Resources/Context object between WebView loading its resources and the point where we try to find the ID of those loaded resources. The officially-supported ways of manipulating resources through the framework AssetManager shouldn't cause this problem ever, and in the past this has always been caused by an app using unsupported platform APIs to do things it shouldn't.

The crash log shows this happening in Facebook as well; if it's happening in multiple apps at the same time that's pretty suspicious and might suggest there is some failure mode we don't know about that *is* related to webview updates.. we should investigate this.

Does this reproduce reliably? You haven't mentioned what device or exact OS version you're using.

s.patwari@, shivam.t@, which device do you get this crash on?

@s.patwari: Can you confirm, are you still able to reproduce the issue using latest version #63.0.3239.111.

Thanks!!

***Bulk Edit***

There is no valid investigation in the bug, closing. Feel free to reopen if needed.