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 246315 - Evo crashed adding a task
Evo crashed adding a task
Status: RESOLVED DUPLICATE of bug 245236
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-07-14 17:20 UTC by skadz
Modified: 2003-07-15 23:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description skadz 2003-07-14 17:20:44 UTC 
Package: Evolution
Priority: critical
Version: GNOME2.2.2 1.4.3
os_details: Ximian, Inc.
Synopsis: Evo crashed adding a task
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
Evo 1.4.3 on RH 8.0 with XD2.

Was cleaning up my tasks (as I do most Mondays) and after changing due
dates on a number of tasks, as well as marking some as done, I went to
add a few tasks, the first one added fine, the second one crashed evo.

Steps to reproduce the problem:
1.  Go to Tasks
2. Change Due Dates on a number of tasks
3. Check off some tasks as done
4. Add some tasks

Actual Results:
Second add crashed evolution, though task seemed to be added fine.

Expected Results:
Task should be added and evolution should keep on chugging along.

How often does this happen?
Once so far.

Additional Information:
I've seen what seem to be A LOT of issues with tasks in Evolution.  I
keep a lot in my task list and use it often.  Seems like there are a
number of memory leaks in both evolution and wombat when dealing with
tasks (seen memory usage double and triple in wombat just by changing
the due date of a task) as well.


Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 1861)]
[New Thread 32769 (LWP 1869)]
[New Thread 16386 (LWP 1870)]
[New Thread 32771 (LWP 1871)]
[New Thread 49156 (LWP 1872)]
[New Thread 81925 (LWP 1885)]
[New Thread 98310 (LWP 1886)]
[New Thread 114695 (LWP 1887)]
[New Thread 131080 (LWP 1888)]
[New Thread 147465 (LWP 1889)]
[New Thread 163850 (LWP 1890)]
[New Thread 180235 (LWP 1891)]
[New Thread 196620 (LWP 1892)]
[New Thread 213005 (LWP 1893)]
[New Thread 262158 (LWP 1924)]
0x404eb83a in waitpid ()
   from /lib/i686/libpthread.so.0

+ Trace 38687

Thread 1 (Thread 16384 (LWP 1861))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 evolution_storage_set_view_factory_new_view
  • #3 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #4 <signal handler called>
  • #5 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_widget_get_child_visible
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_widget_has_screen
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_entry_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #10 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #16 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 waitpid
    from /lib/i686/libpthread.so.0 



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Gerardo Marin 2003-07-15 23:45:56 UTC 

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