Closed ligi closed 6 years ago
Can you give some details about the hardware and how often it crashes? This looks like yet another Go runtime issue. Not sure why it's always you who is affected by these.
This particular crash was on a galaxy note 4 and I only had this crash once so far. I think I get these crashes more often as I maybe using go-ethereum with the in-process node on android the most? On the rinkeby stats at https://stats.rinkeby.io e.g. I only see myself with android ( GethDroid/v1.6.0-stable/android-amd64/go1.8.1 ) - Or I am the only one reporting these?
Thanks!
Completely unrelated, but why the heck is the travis build path in the crash dump?!
GethDroid/v1.6.0-stable/android-arm/go1.8.1 in the stats page is the emulator I use most of the time currently. There I never had this issue so far and use it way more often than the phone. Mainly using the phone when needing to test the whole qr-code stuff - scanning is easier with a phone. The crash happened on a Galaxy Note 4 - not sure how this shows up in the stats - can check after I got my first tea
Not sure what the travis build path is doing in the dump. I do not use travis for building - I use kontinuum. Must be coming from the build-pipeline that builds the geth aar for maven-central.
I have some more info regarding this one as I now could produce this more often. It was not happening on my emulator that I use normally because this one has a lot of ram. A current sync from genesis on my note 7 - I get a lot of these crashes. Then I was looking at the memory monitor in Android-Studio:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
System information
Geth version: 1.6.0 OS & Version: Android
Expected behaviour
should not crash
Actual behaviour
crashes
Backtrace