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 366128 - 100% cpu usage with gnomevfs apps
100% cpu usage with gnomevfs apps
Status: RESOLVED DUPLICATE of bug 357704
Product: gnome-vfs
Classification: Deprecated
Component: Monitoring (inotify)
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: John McCutchan
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 07:06 UTC by James "Doc" Livingston
Modified: 2006-10-29 04:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James "Doc" Livingston 2006-10-28 07:06:57 UTC
I've been noticing that several gnome-vfs apps randomly begin to use 100% cpu, and restarting the app is the only method of stopping it.

After some investigation, what appears to be happening is that in libgnomevfs/gnome-vfs-monitor.c actually_dispatch_callback() gets called and no_live_callbacks() returns FALSE, so install_timeout() gets called. In install_timeout, delay is 0, so it installs the idle timeout. This then repeats forever with the idle callbacks consuming the CPU.

I haven't figured out why no_live_callbacks doesn't ever return TRUE yet. Any suggestions on what to look for when debugging would be much appreciated.
Comment 1 Josselin Mouette 2006-10-28 13:28:17 UTC
Looks like a duplicate of bug#357704. I'm still clueless as to what is causing this. Reverting the patch from bug#341585 may be an option.
Comment 2 James "Doc" Livingston 2006-10-29 04:40:25 UTC
Yeah, from the descripton and traces it looks identical, so marking as a dupe.

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