还没有体验过 ARM QQ
观察下来消息前后的系统内存、IO、CPU 等变化看看，排除下性能方面导致崩溃的可能

@Spoony linuxqq刚出来的时候，我用s905l3a的电视盒子玩过了，可以用，可以聊天，只是切聊天窗口的时候cpu占满，没其他问题，linuxqq x86平台还可以，只有极个别的桌面环境有问题，大部分还可以。linuxqq刚测试的时候我就在用了。用到现在。

错误消息记录在~/.../crash_files/map_record.txt reg_record.txt rqd_record.eup tomb_1682153439482.txt中，这是错误的最后几行：
......
235,1398,Read map line: 7f88289000-7f8828a000 r--p 00021000 b3:02 3339 /usr/lib/aarch64-linux-gnu/ld-2.31.so

235,1399,Read map line: 7f8828a000-7f8828c000 rw-p 00022000 b3:02 3339 /usr/lib/aarch64-linux-gnu/ld-2.31.so

235,1400,Read map line: 7fcf71d000-7fcf74e000 rw-p 00000000 00:00 0 [stack]

[BuglyService.cpp][handleSignal][382]Stack is succesfully dumped by libUnwind.
[BuglyService.cpp][handleSignal][384]Native stack:
$$00 pc 0000000002075c80 /opt/QQ/qq [arm64-v8a::e1c1dee543bceb3e3888e876381249a8]
$$01 pc 0000000002075c14 /opt/QQ/qq [arm64-v8a::e1c1dee543bceb3e3888e876381249a8]

[BuglyService.cpp][handleSignal][386]Record map file of thread: 9679
[BuglyService.cpp][handleSignal][396]Dumping of native stack finished.
235,0001,Record EupInfo
235,0002,EupInfo has been recorded.
235,0003,Record native key-value list.
235,0004,Native key-value list has been recorded.
235,0005,Record native log.
235,0000,Native log has not been initiated.
235,0006,Native log has been recorded.
[BuglyService.cpp][clearEupInfo][283]Clear eupInfo object.
235,0005,Try to unlock file: /home/pi/.config/QQ/crash_files//../files/native_record_lock
235,0006,Successfully unlock file: /home/pi/.config/QQ/crash_files//../files/native_record_lock
[BuglyService.cpp][handleSignal][441]Restored signal handlers.

已经解决，参考：https://bbs.archlinuxcn.org/viewtopic.php?id=13229，使用dunst接管系统通知即可