Several bugs (Vanadium crashing, kernel panic, Couldn't save screenshots)

blackpill

My P8P on the stable GOS release channel has become a bit of a nightmare this past couple of weeks. I've had several Vanadium crashes (i can re-pro one of them fairly often), a random kernel panic, inability to save screenshots, and some other rando bugs that I see listed on GH.

i've dumped the logs after a couple of the crashes. Haven't had the time just yet to dissect them, but my GH account is evidently blocked by the GOS project so I can't even report them directly.

Is anyone else seeing anything like this on their devices? I start twitching a bit when my browser and kernels crash on me.

de0u

blackpill Haven't had the time just yet to dissect them, but my GH account is evidently blocked by the GOS project so I can't even report them directly.

GitHub shadow-bans accounts with throwaway (or otherwise suspicious) e-mail addresses. If that's what's happening, you can try adding a "real" (as defined by GitHub) e-mail address to your account.

fid02

blackpill i can re-pro one of them fairly often

That's interesting. If you have steps to reproduce, it might be useful to provide them, so that others can try to do the same and see if they get the crash.

blackpill

de0u yeah it's very strange, because I've been using this GH account since 2009 with the same emal@domain.tld the entire time. Always using best practices for auth, project security, IdM, etc. In any event,, I'm going to contact GH support (I'm a paying customer afterall).

blackpill

fid02 the most consistent means to re-pro is double-tapping or triple-tapping text areas like the Vanadium address bar, Discourse forum WYSIWYG editors to highlight text. This started happening around the same time that I noticed this bug also affecting my device (using the default GOS/AOSP keyboard though):

https://github.com/GrapheneOS/os-issue-tracker/issues/4223

fid02

blackpill the most consistent means to re-pro is double-tapping or triple-tapping text areas like the Vanadium address bar, Discourse forum WYSIWYG editors to highlight text.

Oh. That is unfortunately (or perhaps fortunately) very much not reproducible on my end.

de0u

blackpill Since fid02 hasn't been able to reproduce, can you provide more details? Are you perhaps using a non-default keyboard app? Have you specified any non-English language preferences? Of course things like that should work, but this sort of information might be useful in figuring out what's going on.

blackpill

These reproducible Vanadium crashes continue. I can trigger them by double or triple tapping a misspelled word in Discourse and Xenforo WYSIWYG editors while composing message replies.

type: crash
userType: full.secondary
osVersion: google/husky/husky:15/AP3A.241005.015/2024103100:user/release-keys
uid: 1210097 (u:r:untrusted_app:s0:c97,c256,c524,c768)
cmdline: app.vanadium.browser
processUptime: 153s

abortMessage: [FATAL:check.cc(361)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

signal: 5 (SIGTRAP), code 1 (TRAP_BRKPT), faultAddr d3e03c54883c
threadName: anadium.browser
MTE: enabled

backtrace:
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 4efa83c)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 619a910)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 65614d0)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 4eee3c4)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 4eee488)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 619a46c)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 61ae63c)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 49d298c)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 49d5d30)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 655e124)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 656184c)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 7764510)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 52153c4)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 5213aa0)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 661e0f8)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 661cd68)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 521dd44)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 61ec1a8)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 4f601e8)
    /product/app/TrichromeLibrary/TrichromeLibrary.apk!libmonochrome_64.so (pc 4f5fd94)
    /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+1524, pc 13614)
    /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+48, pc 195c80)
    /system/framework/arm64/boot-framework.oat (art_jni_trampoline+112, pc 1ece80)
    /system/framework/arm64/boot-framework.oat (android.os.MessageQueue.next+256, pc 52c3a0)
    /system/framework/arm64/boot-framework.oat (android.os.Looper.loopOnce+88, pc 529c58)
    /system/framework/arm64/boot-framework.oat (android.os.Looper.loop+244, pc 529b84)
    /system/framework/arm64/boot-framework.oat (android.app.ActivityThread.main+1572, pc 2f88f4)
    /apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+640, pc 38d640)
    /apex/com.android.art/lib64/libart.so (_jobject* art::InvokeMethod<(art::PointerSize)8>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jobject*, _jobject*, unsigned long)+744, pc 388ff8)
    /apex/com.android.art/lib64/libart.so (art::Method_invoke(_JNIEnv*, _jobject*, _jobject*, _jobjectArray*) (.__uniq.165753521025965369065708152063621506277)+36, pc 6f36e4)
    /system/framework/arm64/boot.oat (art_jni_trampoline+116, pc a2114)
    /system/framework/arm64/boot-framework.oat (com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run+116, pc 7ffa34)
    /apex/com.android.art/lib64/libart.so (nterp_helper+7636, pc 7a8c44)
    /system/framework/framework.jar (com.android.internal.os.ExecInit.main+88, pc 1c5044)
    /apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+640, pc 38d640)
    /apex/com.android.art/lib64/libart.so (art::JNI<false>::CallStaticVoidMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+976, pc 767770)
    /system/lib64/libandroid_runtime.so (_JNIEnv::CallStaticVoidMethod(_jclass*, _jmethodID*, ...)+108, pc dd69c)
    /system/lib64/libandroid_runtime.so (android::AndroidRuntime::callMain(android::String8 const&, _jclass*, android::Vector<android::String8> const&)+340, pc f0404)
    /system/bin/app_process64 (android::AppRuntime::onStarted()+72, pc 49e8)
    /system/framework/arm64/boot-framework.oat (art_jni_trampoline+104, pc 1ed198)
    /apex/com.android.art/lib64/libart.so (nterp_helper+152, pc 7a6f08)
    /system/framework/framework.jar (com.android.internal.os.RuntimeInit.main+48, pc 1d4818)
    /apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+640, pc 38d640)
    /apex/com.android.art/lib64/libart.so (art::JNI<false>::CallStaticVoidMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+976, pc 767770)
    /system/lib64/libandroid_runtime.so (_JNIEnv::CallStaticVoidMethod(_jclass*, _jmethodID*, ...)+108, pc dd69c)
    /system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vector<android::String8> const&, bool)+908, pc f403c)
    /system/bin/app_process64 (main+1228, pc 45ac)
    /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+120, pc 602e8)```

[deleted]

blackpill userType: full.secondary

Do you have the same issue in the owner profile?

blackpill

de0u I'm on a very minimal / stock GOS running the latest stable on a P8P. I saw that some others opened issues on the GOS Github for Vanadium though reporting similar error logs:

https://github.com/GrapheneOS/Vanadium/issues/645

For whatever reason, I cannot post or even give a +1 to anything on the GOS Github projects. I opened a ticket with Github a few days ago and haven't heard anything back from them, so meh.

de0u

blackpill For whatever reason, I cannot post or even give a +1 to anything on the GOS Github projects.

Odd! How about other projects?

blackpill

de0u It has to be something with the GOS org-level settings. I'm blocked from all GOS projects, and I only vaguely remember seeing this same error for one other project a long time ago. I've had this account since Github.com first launched (15+ years at least) and have been an admin / owner of several large enterprise projects / orgs in the past.

Opened a ticket with Github on the outside chance that there was something on my end, but I don't expect them to triage my ticket anytime soon.

blackpill

[deleted] it also crashes in owner 100% of the time.

This might to have something to do with the autocorrect popup menu. If you try and put the cursor on a mistyped word and trigger the autocorrect menu to popup, and if you tap between letters or like you're trying to highlight the entire word before the autocorrect menu pops up - crash time. It also seems like it could be some kind of race condition where the autocorrect popup and the cut copy paste select all dialogue are trying to fire at the same time and causing something in libmonochrome_64 to hit an unexpected or invalid state.

This never happened prior to this Android 15 update :(

blackpill

There's doesn't seem to be any related issues filed upstream for this bug:

https://issues.chromium.org/issues?q=libmonochrome_64.so&s=modified_time:desc&p=1

blackpill

Resolved https://github.com/GrapheneOS/Vanadium/issues/642