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 576654 - Crashed when marking mail as spam
Crashed when marking mail as spam
Status: RESOLVED DUPLICATE of bug 569700
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-03-25 05:29 UTC by Priit Laes (IRC: plaes)
Modified: 2009-03-27 15:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
test patch (976 bytes, text/plain)
2009-03-26 12:37 UTC, Milan Crha 		Details

Description Priit Laes (IRC: plaes) 2009-03-25 05:29:04 UTC 
What were you doing when the application crashed?
Crashed when marking mail as spam


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.26.0 2009-03-20 (Gentoo)
BugBuddy Version: 2.26.0

System: Linux 2.6.28 #134 SMP PREEMPT Sat Dec 27 13:16:10 EET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Compact
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 797827072 vsize: 797827072 resident: 75341824 share: 25169920 rss: 75341824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237958246 rtime: 1126 utime: 990 stime: 136 cutime:41 cstime: 45 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7fb11a8ed750 (LWP 22848)]
[New Thread 0x7fb0fce33950 (LWP 23173)]
[New Thread 0x7fb0f1072950 (LWP 22902)]
[New Thread 0x7fb0f0088950 (LWP 22901)]
[New Thread 0x7fb0f25a3950 (LWP 22871)]
[New Thread 0x7fb0f2da4950 (LWP 22870)]
[New Thread 0x7fb0f35a5950 (LWP 22869)]
[New Thread 0x7fb0f3da6950 (LWP 22868)]
[New Thread 0x7fb0f45a7950 (LWP 22867)]
[New Thread 0x7fb0f4fb8950 (LWP 22866)]
[New Thread 0x7fb0f67fc950 (LWP 22863)]
[New Thread 0x7fb0f6ffd950 (LWP 22861)]
[New Thread 0x7fb0f77fe950 (LWP 22860)]
[New Thread 0x7fb0f7fff950 (LWP 22859)]
[New Thread 0x7fb0fe05f950 (LWP 22856)]
[New Thread 0x7fb0fe860950 (LWP 22854)]
0x00007fb1176e755f in __libc_waitpid (pid=23185, stat_loc=0x7fff2293bdb0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 213830

Thread 2 (Thread 0x7fb0fce33950 (LWP 23173))

  • #0 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 130
  • #1 _L_lock_102
    from /lib/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 86
  • #3 <signal handler called>
  • #4 camel_mime_parser_read
    at camel-mime-parser.c line 655
  • #5 stream_read
    at camel-http-stream.c line 487
  • #6 emfh_gethttp
    at em-format-html.c line 531
  • #7 efh_format_exec
    at em-format-html.c line 1304
  • #8 mail_msg_proxy
    at mail-mt.c line 520
  • #9 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #10 g_thread_create_proxy
    at gthread.c line 635
  • #11 start_thread
    at pthread_create.c line 297
  • #12 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #13 ?? 






Comment 1


Akhil Laddha





          2009-03-26 03:50:14 UTC
        



Looks like bug 569700 has been fixed completely. 






Comment 2


Milan Crha





          2009-03-26 09:37:15 UTC
        



(In reply to comment #1)
> Looks like bug 569700 has been fixed completely. 
                         ^ not ^

err :(

I think I noticed it too, it's only quite hard to invoke intentionally.






Comment 3


Milan Crha





          2009-03-26 12:37:11 UTC
        



Created attachment 131429 [details]
test patch

for evolution-data-server;

I do not expect you can trigger this intentionally, but please try to apply this test patch and watch the console whether you'll see there some message with "stream_read: http" at the beginning, it'll show what failed. If it was because of this, then it will not crash. To test even better, comment those new calls of http_disconnect(http); there (3 times). Catch me on IRC, if you have any question. Thanks.






Comment 4


Milan Crha





          2009-03-27 15:19:44 UTC
        



Marking as a duplicate of the initial bug, let's move there. Thanks.

*** This bug has been marked as a duplicate of 569700 ***