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 507792 - crash in Panel: I was calling evolution ...
crash in Panel: I was calling evolution ...
Status: RESOLVED DUPLICATE of bug 489288
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-07 08:38 UTC by Raphael Hertzog
Modified: 2008-01-09 22:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Raphael Hertzog 2008-01-07 08:38:48 UTC
Version: 2.20.2

What were you doing when the application crashed?
I was calling evolution --force-shutdown because evolution-data-server leaked too much (it was using 1.5GB of RAM...).

I'm pretty sure the clock applet is at fault. FWIW, I have a caldav calendar in evolution that clock-applet is accessing. Maybe the memory leak in evolution-data-server is also related to this usage of a caldav calendar.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 73719808 vsize: 73719808 resident: 17600512 share: 8613888 rss: 17600512 rss_rlim: 4294967295
CPU usage: start_time: 1198655344 rtime: 55413 utime: 51572 stime: 3841 cutime:225 cstime: 20 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f236b0 (LWP 4552)]
[New Thread 0xb49feb90 (LWP 17749)]
[New Thread 0xb63abb90 (LWP 1296)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6f236b0 (LWP 4552))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__g_slist_remove
    at /tmp/buildd/glib2.0-2.14.4/glib/gslist.c line 207
  • #7 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 IA__g_value_peek_pointer
    at /tmp/buildd/glib2.0-2.14.4/gobject/gvalue.c line 185
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.4/gobject/gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.4/gobject/gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.4/gobject/gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.4/gobject/gsignal.c line 2199
  • #16 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.4/gobject/gsignal.c line 2243
  • #17 ??
    from /usr/lib/libecal-1.2.so.7
  • #18 ??
  • #19 ??
  • #20 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (437223 sec old) ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointe
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-09 22:07:14 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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