After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722182 - [abrt] Possible memory corruption after move of messages in GMail IMAP
[abrt] Possible memory corruption after move of messages in GMail IMAP
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-01-14 14:11 UTC by Milan Crha
Modified: 2015-08-07 08:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2014-01-14 14:11:34 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1036264

Description of problem:
GMail got stuck as usual (moving emails from one IMAP folder to another does not do anything, at some point "pinging the server" is displayed in the status bar); hence I pressed "Cancel all".

Version-Release number of selected component:
evolution-3.10.2-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        evolution
crash_function: _g_list_remove_link
executable:     /usr/bin/evolution
kernel:         3.11.9-300.fc20.i686+PAE

Core was generated by `evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 233029

Thread 1 (Thread 0xb0ee0900 (LWP 2618))

  • #0 _g_list_remove_link
    at glist.c line 433
  • #1 g_list_delete_link
    at glist.c line 561
  • #2 e_source_registry_list_sources
    at e-source-registry.c line 2708
  • #3 em_utils_folder_is_sent
    at e-mail-utils.c line 233
  • #4 update_1folder
    at mail-folder-cache.c line 820
  • #5 folder_changed_cb
    at mail-folder-cache.c line 960
  • #6 g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 1198
  • #7 g_closure_invoke
    at gclosure.c line 777
  • #8 signal_emit_unlocked_R
    at gsignal.c line 3586
  • #9 g_signal_emit_valist
    at gsignal.c line 3330
  • #10 g_signal_emit
    at gsignal.c line 3386
  • #11 folder_emit_changed_cb
    at camel-folder.c line 198
  • #12 g_idle_dispatch
    at gmain.c line 5251
  • #13 g_main_dispatch
    at gmain.c line 3066
  • #14 g_main_context_dispatch
    at gmain.c line 3642
  • #15 g_main_context_iterate
    at gmain.c line 3713
  • #16 g_main_loop_run
    at gmain.c line 3907
  • #17 gtk_main
    at gtkmain.c line 1158
  • #18 main
    at main.c line 683 






Comment 1


Milan Crha





          2014-01-14 14:17:26 UTC
        



Maybe related, took from the same downstream bug report:





+
Trace
    233030
















Comment 2


Milan Crha





          2015-08-07 08:36:22 UTC
        



The code in question is gone since the changes for bug #745545. I also tried to reproduce the crash wit an address sanitizer on, but it didn't claim anything, which might be eventually fine, though I cannot reproduce many crashes which the users face.

I'm closing this, in a favour of bug #745545, but also because there was no duplicate for a long time.