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 642382 - Crash in imapx_job_done, imapx_command_sync_changes_done
Crash in imapx_job_done, imapx_command_sync_changes_done
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
: 642380 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-02-15 15:13 UTC by Brian J. Murrell
Modified: 2013-08-22 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian J. Murrell 2011-02-15 15:13:15 UTC 
I don't really know where/why this one crashed.

I think I'm starting to regret moving to 2.32.2 especially considering the file layout changes it entailed.  Going back to 2.30.3 would be a pain I think.  ~sigh~

But this has been 2 crashes in about 20 minutes now.

+ Trace 225975

Thread 25 (Thread 14085)

  • #0 __strcmp_ia32
    at ../sysdeps/i386/i686/multiarch/../strcmp.S line 56
  • #1 camel_folder_summary_check_uid
    at camel-folder-summary.c line 1150
  • #2 message_info_from_uid
    at camel-vee-summary.c line 339
  • #3 camel_folder_summary_uid
    at camel-folder-summary.c line 1322
  • #4 folder_get_message_info
    at camel-folder.c line 649
  • #5 camel_folder_get_message_info
    at camel-folder.c line 1656
  • #6 folder_changed_add_uid
    at camel-vee-folder.c line 162
  • #7 folder_changed_change
    at camel-vee-folder.c line 418
  • #8 session_thread_proxy
    at camel-session.c line 321
  • #9 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.26.0/glib/gthreadpool.c line 319
  • #10 g_thread_create_proxy
    at /build/buildd/glib2.0-2.26.0/glib/gthread.c line 1897
  • #11 start_thread
    at pthread_create.c line 304
  • #12 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Thread 1 (Thread 14011)

  • #0 __pthread_mutex_lock
    at pthread_mutex_lock.c line 50
  • #1 g_async_queue_lock
    at /build/buildd/glib2.0-2.26.0/glib/gasyncqueue.c line 251
  • #2 camel_msgport_push
    at camel-msgport.c line 359
  • #3 camel_msgport_reply
    at camel-msgport.c line 494
  • #4 imapx_job_done
    at camel-imapx-server.c line 2036
  • #5 imapx_command_sync_changes_done
    at camel-imapx-server.c line 4538
  • #6 imapx_completion
    at camel-imapx-server.c line 1939
  • #7 imapx_step
    at camel-imapx-server.c line 1963
  • #8 parse_contents
    at camel-imapx-server.c line 4681
  • #9 imapx_parser_thread
    at camel-imapx-server.c line 4748
  • #10 g_thread_create_proxy
    at /build/buildd/glib2.0-2.26.0/glib/gthread.c line 1897
  • #11 start_thread
    at pthread_create.c line 304
  • #12 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130 






Comment 1


Akhil Laddha





          2011-02-16 03:52:07 UTC
        



*** Bug 642413 has been marked as a duplicate of this bug. ***






Comment 2


Akhil Laddha





          2011-02-16 03:52:13 UTC
        



*** Bug 642380 has been marked as a duplicate of this bug. ***






Comment 3


Michel Dänzer





          2011-03-03 09:40:53 UTC
        



I also hit this occasionally. Backtrace below, looks like msgport->queue is bogus in camel_msgport_push(). Maybe the object pointed to by msgport was already destroyed?

This seems to be a regression in 2.32, at least I never saw it before.





+
Trace
    226178






    

  • 
#0
g_atomic_int_get

    
                at /build/buildd-glib2.0_2.28.1-1+b1-powerpc-ecGhBx/glib2.0-2.28.1/./glib/gatomic-gcc.c
                  line
                  64

    

    • 

  • 
#1
g_async_queue_lock

    
                at /build/buildd-glib2.0_2.28.1-1+b1-powerpc-ecGhBx/glib2.0-2.28.1/./glib/gasyncqueue.c
                  line
                  249

    

    • 

  • 
#2
camel_msgport_push

    
                at camel-msgport.c
                  line
                  359

    

    • 

  • 
#3
camel_msgport_reply

    
                at camel-msgport.c
                  line
                  494

    

    • 

  • 
#4
??

    
                from
                /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimapx.so

    

    • 

  • 
#5
??

    
                from
                /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimapx.so

    

    • 

  • 
#6
??

    
                from
                /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimapx.so

    

    • 

  • 
#7
??

    
                from
                /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimapx.so

    

    • 

  • 
#8
??

    
                from
                /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimapx.so

    

    • 

  • 
#9
g_thread_create_proxy

    
                at /build/buildd-glib2.0_2.28.1-1+b1-powerpc-ecGhBx/glib2.0-2.28.1/./glib/gthread.c
                  line
                  1897

    

    • 

  • 
#10
start_thread

    
                at pthread_create.c
                  line
                  302

    

    • 

  • 
#11
clone

    
                at ../sysdeps/unix/sysv/linux/powerpc/powerpc32/clone.S
                  line
                  123

    

    • 













Comment 4


Milan Crha





          2011-10-19 07:22:44 UTC
        



Similar downstream bug report from 2.32.3:
https://bugzilla.redhat.com/show_bug.cgi?id=746963






Comment 5


Michel Dänzer





          2011-10-19 15:05:59 UTC
        



FWIW, this seems fixed in latest 3.0.x.






Comment 6


Matthew Barnes





          2013-08-22 17:12:33 UTC
        



Closing as OBSOLETE per comment 5.