#854667 icedove: SIGSEGV, from /usr/lib/icedove/libxul.so

Package:
icedove
Source:
thunderbird
Submitter:
Jean-Francois Pirus
Date:
2023-04-25 08:54:30 UTC
Severity:
important
#854667#5
Date:
2017-02-09 10:02:37 UTC
From:
To:
Crash when switching emails.

Linux Tosh 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux

backtrace included
#854667#10
Date:
2017-02-09 21:40:24 UTC
From:
To:
Hi,

unfortunately this log is quite useless, do you have icedove-dbg installed?

Please use the method described in the wiki, otherwise a lot needed
informations are wrapped.

https://wiki.debian.org/Icedove#Debugging

Regards
Carsten
#854667#15
Date:
2017-02-10 06:44:59 UTC
From:
To:
You are correct icedove-dbg was not installed, sorry about that. (It was
installed on my other workstation)

Should probably close this bug as I can't replicate it with icedove-dbg
loaded, or it doesn't mention libxul.so when it's loaded.

Thanks.
#854667#20
Date:
2017-03-14 12:54:54 UTC
From:
To:
Hi,

same here, have this crashes since a few weeks or so, and I think they
appeared after a package upgrade. They occur every few minutes to hours
and seem to be random. It doesn't crash if strace is attached, though.
Today I installed icedove-dbg and had it running in the shell as
"icedove -safe-mode" and got a core file. BT attached, thread 1 shows
the sig 11.

It's running in gdb now as recommended in the Wiki, but I'm afraid it
will not crash there.

Cheers,
Daniel
#854667#25
Date:
2017-03-14 19:55:02 UTC
From:
To:
Hi,

now after a restart it crashed quite quickly. Attached you can find
the gdb log. The BT doesn't look helpful though. Let me know if you
need more information or if there's anything I can try.

Cheers,
Daniel
#854667#30
Date:
2017-03-29 09:48:51 UTC
From:
To:
Hi,

is there anything we can do? For whatever reason crashes are happening
less frequently recently, but still it is crashing every few days. Any
effort to get this fixed would be highly appreciated.

Cheers,
Daniel
#854667#35
Date:
2017-03-29 12:23:47 UTC
From:
To:
Hello Daniel,

Am 29.03.2017 um 11:48 schrieb Daniel Tiefnig:

the best for all reports would be to try to categorize the crash reports
and collecting traces that affect the same component. Then forward them
upstream to the Mozilla Bugtracker in case there is no corresponding
issue found to append.

Or, if you are developer with some coding experience, gig into the code
and try to fix some segfault.
One real problem here is to reproduce the crash in a
reproducible way. So that all is no easy task.

If you haven't some experience here there isn't much you can do.
#854667#40
Date:
2017-08-16 09:18:11 UTC
From:
To:
Hi,

just for the record: Since I updated to Stretch on July 30, I didn't
experience any crash so far, while on Jessie it was crashing every
second day on average.

So it looks like at least I got rid of the problem with the upgrade to
52.2.1.

Cheers,
Daniel