Open h2dden opened 8 months ago
Looks like MTE is enabled by default on grapheneos for the pixel 8 - but earlier pixels do not have the required hardware for it. Can it be disabled on an app-by-app basis?
Any idea how to test this, without having a pixel 8?
When exactly does the crash happen? Is it right at launch?
(On the website, on the download page, click "Previous releases" at the top. There you can manually download apks.)
Can it be disabled on an app-by-app basis?
sure, but why would you?
When exactly does the crash happen? Is it right at launch?
upon launch
just tested: Electrum-4.5.0.0-arm64-v8a-release.apk upon launch:
type: crash
osVersion: google/husky/husky:14/UQ1A.231205.015/2023121200:user/release-keys
uid: 1110145 (u:r:untrusted_app_30:s0:c145,c256,c523,c768 )
cmdline: org.electrum.electrum
processUptime: 2s
signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr 100d8ca59a92020
threadName: qtMainLoopThrea
MTE: enabled
backtrace:
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (pc 1801a0)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (pc 16a470)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (PyDict_SetDefault+500, pc 16cf98)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (PyUnicode_InternInPlace+116, pc 1a3b40)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (PyUnicode_InternFromString+60, pc 1c23a0)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (PyType_Ready+404, pc 18e6d0)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (_PyTypes_Init+24, pc 17ead8)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (Py_InitializeFromConfig+1000, pc 23bc88)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libpython3.8.so (Py_InitializeEx+128, pc 23bf98)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libmain.so (main+952, pc 3240)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so (pc 4c748)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/oat/arm64/base.odex (art_jni_trampoline+112, pc 27a150)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/oat/arm64/base.odex (org.qtproject.qt.android.QtNative$7.run+36, pc 277374)
/data/app/~~T1x4tgyly0ys47PQOqPNlQ==/org.electrum.electrum-0DZpCrtWuehjdS6U2eNTqA==/oat/arm64/base.odex (org.qtproject.qt.android.QtThread$1.run+640, pc 281270)
/system/framework/arm64/boot.oat (java.lang.Thread.run+72, pc 15f828)
/apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+612, pc 2109a4)
/apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+172, pc 253b3c)
/apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+1416, pc 69abc8)
/apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cffec)
/apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 64d30)
could not install 4.3.4 says package is not valid
Thanks for testing.
Looking at the traceback, it might help if we updated the python interpreter.
Can it be disabled on an app-by-app basis?
sure, but why would you?
To be able to use the application, as a workaround. This might not get fixed until someone who has hardware for it decides to contribute.
memory tagging is enabled by default: haven't changed anything. there is not much to be changed apart from disabling on an app by app case in the meanwhile, I am using the desktop/debian package: no time lost here
Looking at the traceback, it might help if we updated the python interpreter.
Python has some stability issues on android. Here are a few crash reports from the play store:
Just attempted to install and use Electrum 4.5.5 on GrapheneOS on the Pixel 8 and got a memory tagging error, too. I'm not knowledgeable enough to know if this helps, but I figured I'd provide some data where I can.
What are the odds this will get fixed? I'm nervous about using an app for money management that can't satisfy modern security standards
Running 4.4.6.0 on GrapheneOS on Pixel 8pro