GNOME Bugzilla – Bug 160737
gilotd crashes constantly
Last modified: 2006-08-08 18:30:37 UTC
Distribution: Debian 3.1 Package: gnome-pilot Severity: normal Version: GNOME2.8.1 2.0.10 Gnome-Distributor: Debian Synopsis: gilotd crashes constantly Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: 2.0.10 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: From the best that I can detect while backing up my Tunsgsten T palm, the evolution-data-server-1.0 keeps grabbing more and more memory, the CPU level goes really high, and gpilotd competes with the evolution-data-server to grab as much memory as it can. I am not sure if this is related, but if you watch evolution while the sync is taking place, you will see that the TODO database (this is the only observable one) is growing by leaps and bounds. Somehow, blank "To Do" items are being generated. In one of my attempts, I ended up with well over 3000 blank "To Do" items before I killed gpilotd. Steps to reproduce the crash: 1. Hit the sync button on the palm 2. Watch the fireworks Expected Results: A successful sync How often does this happen? All the time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gpilotd' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-07 17:36 ------- Unknown version 2.0.10 in product gnome-pilot. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-pilot". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. It appears that the stack trace didn't make it. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
I looked closely at the "crashing". Gpilotd is actually not crashing, I just discovered. The real problem is that between evolution-data-server and gpilotd, somehow they are generating thousands of blank entries on the palm, and thus this would run for a very long time and until all my physical and virtual memory was exhausted. Thus, it wasn't that gpilotd was crashing or hanging. Rather, it was that huge amounts of data are being handled. I just found about 10,000 blank entries in my Palm's calendar, on date Dec 31, 2027 (confirmed by the Windows sync software). I also just found another 5,000 blank entries on my To Do list. I hope that this helps.
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Subodh: What extra information exactly are you looking for? And how would the reporter get it?
Could this bug be related to the empty todos creation as described in bug 161798 ? Just an observation, as in both the bug reports empty Todos items are getting created.
*** This bug has been marked as a duplicate of 271969 ***