New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/mobile: loading webviewchromium after Go.init crashes on 5.0.1 #9507
Comments
the ownership of signal handlers is going to be an issue when |
I believe the basic signal forwarding added in https://golang.org/cl/8712 (5c8fbc6) takes care of this. |
I don't think this is resolve unless my issue is related to something separate. I'm still experiencing a crash that's the same as the original reported. If a sample app would be helpful, I'd be happy to produce this based on the latest gomobile bits. I tested this against golang: a81c656 producing an aar from such for inclusion in a project |
sorry, updating the original but go hash is: a81c656 |
If you can provide a failing program I'll take a look next week. |
ok, will do, as a heads up, the program will use RecyclerView to interlace PublisherAdView's in a stream of stories (such as slashdot) which should reproduce the issue. |
Looking into #12725, I guess this is related to misuse of the context. |
After
Go.init(this)
, attempting to callPublisherAdView.loadAd
fromcom.google.android.gms:play-services:6.5.87
causes crash on 5.0.1 but not previous 4.x versions of android.PublisherAdView
uses aWebView
to load ads.Very little information is provided in logcat on crash
Notable is
E/libsigchain﹕ Warning: Unexpected sigaction action found 0xaff5decc
after webviewchromium loads native code, which is an error from the ART runtime: https://android.googlesource.com/platform/art/+/master/sigchainlib/sigchain.cc#161I believe that's why 4.x is not affected. I was not able to reproduce this issue with the sole use of a simple
WebView
loading a website.I have found that allowing a single
PublisherAdView.load
call to complete successfully (to allow webviewchromium native code to load first) followed byGo.init
does work successfully, including afterwards creating new ad views and more calls toPublisherAdView.load
.I'll put together a minimal sample soon.
The text was updated successfully, but these errors were encountered: