Vanadium keeps crashing on ERPNext sites

Matth

Since this morning, I can't use my ERPNext sites anymore on my Vanadium browser.
Whenever I open the browser, it immediately crashes. With that page being the last one trying to be opened, it just didn't let me do anything, not even close that page.
I tried rebooting the phone, but that didn't help. I then managed to at least close the page by deleting the cache of the app in the app settings.
However, as soon as I try to access it again, it starts to crash again.
Previously I never had an issue, it only started this morning.
How can I use that again? It's a site I really need regularly.

fid02

Matth Providing a crash log might help some people in understanding what is causing the crash.

GrapheneOS

Matth Matth Please update to Vanadium 137.0.7151.72.1 in the App Store Alpha channel. If you still have crashes, open chrome://flags#local-network-access-check and set "Local Network Access Checks" to disabled. The default value on GrapheneOS is "Enabled (Blocking)" since Vanadium Config 75.

Matth

Here is one. I got dozens if necessary. I can literally not use it anymore, cos whenever I open a random website, it crashes immediately.

type: crash
userType: full.secondary
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/cheetah/cheetah:15/BP1A.250505.005.B1/2025052800:user/release-keys'
Revision: 'MP1.0'
ABI: 'arm64'
Timestamp: 2025-06-06 09:23:54.536011734+0800
Process uptime: 5s
Cmdline: app.vanadium.browser
pid: 7757, tid: 7757, name: anadium.browser  >>> app.vanadium.browser <<<
uid: 1010092
tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x0000caa302008d64
    x0  0000000000000000  x1  000000000000001d  x2  0000000000000017  x3  64656e792d706572
    x4  64697361626c652d  x5  2d6e6f697373696d  x6  7469736f706d6f63  x7  0000caa2fe038207
    x8  0000000000000000  x9  3bf83e7b415e4400  x10 ffffffffffffff80  x11 000000000000001f
    x12 3ffffffffffffff2  x13 0000000000000017  x14 0000000000000019  x15 000000000000006f
    x16 0000caa309b10620  x17 0000cdd483ca8700  x18 0000cdd4a4a48000  x19 0000ca9e01cfe040
    x20 0000ca9e00609700  x21 0000ca9e01d01800  x22 0000ca9e00da56e0  x23 0000ca9e01cfe040
    x24 0000f2ed6615d670  x25 0000cdd4a42c4040  x26 0000ca9e02501290  x27 0000f2ed6615d360
    x28 0000cdd4a42c4040  x29 0000f2ed6615d2e0
    lr  0000caa3020087e4  sp  0000f2ed6615d1d0  pc  0000caa302008d64  pst 0000000060001000

39 total frames
...

Log File

Matth

Thank you very much. Setting the flag to disabled did solve the problem, after updating to the latest version.

GrapheneOS

Matth Can you turn the flag back on and then get a crash report from the new version if possible?