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 670868 - [imapx] Recursive call of imapx_command_fetch_message_done
[imapx] Recursive call of imapx_command_fetch_message_done
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.4.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2012-02-27 09:38 UTC by Milan Crha
Modified: 2013-08-22 17:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2012-02-27 09:38:35 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=797360

[abrt] evolution-3.3.90-1.fc17: g_cancellable_is_cancelled: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
crash_function: g_cancellable_is_cancelled
executable:     /usr/bin/evolution
kernel:         3.3.0-0.rc3.git7.2.fc17.x86_64
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           vie 24 feb 2012 21:27:04 COT

+ Trace 229748

Thread 1 (Thread 0x7fb517dfa700 (LWP 14297))

  • #0 g_cancellable_is_cancelled
    at gcancellable.c line 296
  • #1 g_cancellable_set_error_if_cancelled
    at gcancellable.c line 313
  • #2 write_to_prfd
  • #3 camel_stream_write
  • #4 camel_stream_write
  • #5 camel_stream_write_string
  • #6 imapx_command_start
    at camel-imapx-server.c line 524
  • #7 imapx_command_start_next
    at camel-imapx-server.c line 731
  • #8 imapx_command_start_next
    at camel-imapx-server.c line 595
  • #9 imapx_command_queue
    at camel-imapx-server.c line 830
  • #10 imapx_command_fetch_message_done
    at camel-imapx-server.c line 3187
  • #11 imapx_command_start
    at camel-imapx-server.c line 553
  • #12 imapx_command_start_next
    at camel-imapx-server.c line 731
  • #13 imapx_command_start_next
    at camel-imapx-server.c line 595
  • #14 imapx_command_queue
    at camel-imapx-server.c line 830
  • #15 imapx_command_fetch_message_done
    at camel-imapx-server.c line 3187
  • #16 imapx_command_start
    at camel-imapx-server.c line 553
  • #17 imapx_command_start_next
    at camel-imapx-server.c line 731
  • #18 imapx_command_start_next
    at camel-imapx-server.c line 595
  • #19 imapx_command_queue
    at camel-imapx-server.c line 830
  • #1950 imapx_command_fetch_message_done
    at camel-imapx-server.c line 3187
  • #1951 imapx_command_start
    at camel-imapx-server.c line 553
  • #1952 imapx_command_start_next
    at camel-imapx-server.c line 731
  • #1953 imapx_command_start_next
    at camel-imapx-server.c line 595
  • #1954 imapx_command_queue
    at camel-imapx-server.c line 830
  • #1955 imapx_command_fetch_message_done
    at camel-imapx-server.c line 3187
  • #1956 imapx_command_start
    at camel-imapx-server.c line 553
  • #1957 imapx_command_start_next
    at camel-imapx-server.c line 731
  • #1958 imapx_command_start_next
    at camel-imapx-server.c line 595
  • #1959 imapx_command_queue
    at camel-imapx-server.c line 830
  • #1960 imapx_command_fetch_message_done
    at camel-imapx-server.c line 3187
  • #1961 imapx_completion
    at camel-imapx-server.c line 1788
  • #1962 imapx_step
    at camel-imapx-server.c line 1815
  • #1963 parse_contents
    at camel-imapx-server.c line 5130
  • #1964 imapx_parser_thread
    at camel-imapx-server.c line 5177
  • #1965 g_thread_proxy
    at gthread.c line 801
  • #1966 start_thread
    at pthread_create.c line 309
  • #1967 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Milan Crha





          2012-02-27 09:42:11 UTC
        



I suppose this failed on stack overflow, or was close to it, because this:
> imapx_command_start
> imapx_command_start_next
> imapx_command_start_next
> imapx_command_queue
> imapx_command_fetch_message_done
repeats in the backtrace down to frame 1960






Comment 2


Matthew Barnes





          2013-08-22 17:06:47 UTC
        



Closing as OBSOLETE since the stack trace(s) are too old to be useful at this point.