Tom Drewes <[email protected]> writes: > Lengthy description ahead - you have been warned. :-) > > I've run into a situation with a Cordova application that uses the > cordova-plugin-crosswalk-webview (v2.1.0, Crosswalk v21 stable). The > application is used in a kiosk-mode application on an Android tablet. > As such, the application is launched when the tablet is powered up and > locked into kiosk mode so that other applications cannot be switched > to. > > I have observed that sometimes (frequently, but not every time) the > application crashes on tablet power up with the following exception: [...] > Since a configChange doesn't seem to be the culprit, I believe that > sometimes during boot time, as the many processes are spinning up, > Android decides to stop the Cordova activity and restart it, perhaps > due to resource limitations. This restart happens before the Crosswalk > library loading thread is finished, resulting in a different context > for the finishInit() function in XWalkEnvironment. [...] > My question is: can I restructure anything in Android side of my > Cordova app to give Crosswalk the hint the activity has re-started -- > giving it a chance to update the context or otherwise reload the > library? It is currently a vanilla Cordova app, with no customization > of the generated Java code.
I don't have a specific answer to your problem, but am CC'ing some people who might be able to help. In any case, would you mind filing a bug in our issue tracker (crosswalk-project.org/jira) so this doesn't get lost in the mailing list? If you have a small test case we could use to reproduce the issue it'd be even better. _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
