GNOME Bugzilla – Bug 680471
[abrt] Crash under ml_tree_value_at_ex()
Last modified: 2017-08-23 08:35:25 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=841580 [abrt] evolution-3.2.3-3.fc16: ml_tree_value_at_ex: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) libreport version: 2.0.10 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: evolution comment: Try to switch to calendar view crash_function: ml_tree_value_at_ex executable: /usr/bin/evolution time: Thu 19 Jul 2012 16:21:56 EEST Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 230563
Thread 2 (Thread 0x7fbfb6bcd700 (LWP 2540))
Thread 1 (Thread 0x7fbfbe09d980 (LWP 2538))
No duplicate for a long time, I'm closing this.
There had been filled a similar bug report from the latest stable version, 3.18.1: https://bugzilla.redhat.com/show_bug.cgi?id=1273751
+ Trace 235621
Thread 1 (Thread 0x7f9f2c52dac0 (LWP 4638))
The latest backtrace shows that the second thread is finishing folder refresh. It can mean that the values being used in the main (UI) thread had been changed in the second thread. That is that the CamelMessageInfo structure is not thread safe on its own.
And one from 3.20.1: https://bugzilla.redhat.com/show_bug.cgi?id=1333259 This will be addressed with changes from bug #764065 hopefully.
*** Bug 766692 has been marked as a duplicate of this bug. ***
*** Bug 767228 has been marked as a duplicate of this bug. ***
*** Bug 767479 has been marked as a duplicate of this bug. ***
I just got a crash similar to this in 3.20.3-1 from Debian stretch: Core was generated by `evolution'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 236371
Got another crash with this same backtrace.
This is finally addressed (added thread safety around CamelMessageInfo) with changes for bug #764065, which will be released as 3.23.2.
A little correction, comment #8 shows a different issue. I'm reopening bug #767228 for it.
I just got another crash with this backtrace, seems the fix is also in 3.22 git, will there be another release for 3.22 soon?
Which backtrace? There are two different issues in this bug report. That's why I wrote comment #11. The 3.22.3 is planned for December 12th.
I think it was the one from comment #8 again. Thanks for the info, that should be early enough to beat the Debian stretch freeze.
*** Bug 785944 has been marked as a duplicate of this bug. ***