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 336821 - Lockup while "formatting mail" received from myspace.com
Lockup while "formatting mail" received from myspace.com
Status: RESOLVED DUPLICATE of bug 342910
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-04-01 12:25 UTC by gribnick
Modified: 2006-06-05 15:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description gribnick 2006-04-01 12:25:24 UTC
Distribution: Debian testing/unstable
Package: Evolution
Severity: Normal
Version: GNOME2.12.3 unspecified
Gnome-Distributor: Debian
Synopsis: Lockup while "formatting mail" received from myspace.com
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:
Two issues. I was typing along creating a new mail and it died. I have
no idea why. Prior to this, I had several lockups when Evolution went to
display mail from "myspace.com". Even the password reset mail caused it
to lock up. The message "formatting message" at the bottom would be
shown but the process locked tight but was not burning CPU time.


Steps to reproduce the crash:
1. Have myspace.com send you mail
2. Have it attempt to display it in the preview screen.
3. 

Expected Results:
I expect it to work..


How often does this happen?
Today, every single time. I had to edit the mail file and manually
remove the file before evolution would start without hanging.


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230698272 (LWP 24777)]
[New Thread -1281639504 (LWP 24786)]
[New Thread -1273246800 (LWP 24785)]
[New Thread -1245430864 (LWP 24784)]
[New Thread -1263772752 (LWP 24782)]
[New Thread -1255380048 (LWP 24781)]
[New Thread -1237038160 (LWP 24779)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1230698272 (LWP 24777))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #6 g_slice_alloc0
    from /usr/lib/libglib-2.0.so.0
  • #7 g_slist_prepend
    from /usr/lib/libglib-2.0.so.0
  • #8 g_object_get
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_thaw_notify
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #14 gdk_pixmap_get_type
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_thaw_notify
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #20 gdk_pixmap_new
    from /usr/lib/libgdk-x11-2.0.so.0
  • #21 html_gdk_painter_get_type
    from /usr/lib/libgtkhtml-3.8.so.15
  • #22 html_painter_begin
    from /usr/lib/libgtkhtml-3.8.so.15
  • #23 html_engine_intersection
    from /usr/lib/libgtkhtml-3.8.so.15
  • #24 html_engine_expose
    from /usr/lib/libgtkhtml-3.8.so.15
  • #25 gtk_html_get_editable
    from /usr/lib/libgtkhtml-3.8.so.15
  • #26 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #32 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gdk_window_clear_area_e
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #36 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #37 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #41 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #42 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-04-01 12:25 -------

Comment 1 Karsten Bräckelmann 2006-04-01 17:24:37 UTC
Hmm, Debian, lock up at g_slice_alloc()...

Can you please try starting Evolution with the env var mentioned in bug 336767 comment 8? Does this solve your problem?
Comment 2 Jeremy Dinsel 2006-06-05 14:52:59 UTC
Hello. I am affected by this problem, too (see also bug 342910). The solution in bug 336767 comment 8 does resolve the problem for me. In particular, I was looking at a message from Etrade that locked up the formatting process. I'd suggest resolving this bug as a duplicate of bug 342910 as it more accurately describes a generic problem.
Comment 3 Jeffrey Stedfast 2006-06-05 15:03:34 UTC

*** This bug has been marked as a duplicate of 342910 ***
Comment 4 gribnick 2006-06-05 15:13:38 UTC
Shortly after I sent the original bug report I went away on business for over a month so was unable to respond to any further requests for info. On my return, pulling in the latest updates to GTK and other components fixed the issue so I consider this issue closed. It seems to have been a mostly debian specific issue with the order the updates were made in the "testing" environment which then leaked through to ubuntu and others too from what I've read. Thanks for looking..