<amazingfate>
Chromium will only output `elf_dynamic_array_reader.h(64)] tag not found`, no further infos. I tested the same mesa and chromium on qcom sm8250 and rk3568, no such issue
<amazingfate>
kusma: Chromium generates dmp file at `~/.config/chromium/Crash\ Reports/pending/`, and I did convert it to core file with chromium's minidump-2-core, but I can't see useful info when loading the core file with gdb.
<amazingfate>
I also tried to run chromium with env `WAYLAND_DEBUG=1`, but there was no error when crash happened.
<kusma>
OK, then I don't think there's a lot I can help you with, unfortunately
<amazingfate>
I know I should dive into chromium to see what happened, but chromium's debugging is complicated
<kusma>
Yeah, it's really frustrating, and I'm not doing it myself unless I have to ;)
<amazingfate>
running is ozone wayland is necessary for chromium's v4l2 decoding, and now the crash issue just makes mainline chromium on rk3588 unperfect
<amazingfate>
s/running is/running with/g
<amazingfate>
Here is the stacktrace when running chromium with `gdb --args /usr/lib/chromium/chromium --ozone-platform=wayland https://github.com/armbian/linux-rockchip`: "0x0000aaaaafbe283c in partition_alloc::internal::InSlotMetadata::DoubleFreeOrCorruptionDetected(unsigned int) ()"