element-desktop: crashes because probably message search

Steps to reproduce

Sadly - There is no way to reproduce

There is no pattern recognized. It can crash when you do a voice call, it can crash when it’s just in the Background.

It happens really frequent since a week or two

/opt/Element/element-desktop %U
/home/jokergermany/.config/Element exists: yes
/home/jokergermany/.config/Riot exists: no
Starting auto update with base URL: https://packages.element.io/desktop/update/
Auto update not supported on this platform
Fetching translation json for locale: en_EN
Changing application language to de
Fetching translation json for locale: de
Resetting the UI components after locale change
Resetting the UI components after locale change
skipping config: /opt/Element/MangoHud.conf [ not found ]
skipping config: /home/jokergermany/.config/MangoHud/element-desktop.conf [ not found ]
parsing config: /home/jokergermany/.config/MangoHud/MangoHud.conf [ ok ]
MANGOHUD: Connected to D-Bus as ":1.164".
Changing application language to de
Fetching translation json for locale: de
Resetting the UI components after locale change
[11020:0401/131359.127838:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

I suppose this message to syslog has something to do with it: Apr 1 13:39:04 huppyryzen kernel: [ 2396.670871] traps: ThreadPoolForeg[11029] trap int3 ip:55c0dee68224 sp:7f02a11909d0 error:0 in element-desktop[55c0db5e2000+785e000]

I found some messages like this before, but i am not sure if it has something to do with the crash https://www.file-upload.net/download-15122443/_opt_Element_element-desktop.1000.crash.html

Outcome

What did you expect?

Not to crash

What happened instead?

crashed anyway

Operating system

Ubuntu Mate 22.04

Application version

Version von Element: 1.11.26 Version von Olm: 3.2.12

How did you install the app?

No response

No response

Will you send logs?

Yes

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 21 (7 by maintainers)

Most upvoted comments

Argh, sorry my fault. I thought vector-im/element-web#25114 was closed because it was completed, but it was closed as a dup.

Re-opening.

The logic is hard to understand… I opened vector-im/element-web#25114 that has been closed as duplicate of current bug. Now current bug is getting closed as duplicate of vector-im/element-web#25114. There’s a snake eating its own tail problem here…

OK, so I think the re-opened version of this is now a duplicate of vector-im/element-web#25114 and I’m closing it since that one is closed. Please re-open if I’m wrong.