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 659685 - When setting up a group, the daemon eats lots of CPU time and does not respond
When setting up a group, the daemon eats lots of CPU time and does not respond
Status: RESOLVED FIXED
Product: dvb-daemon
Classification: Other
Component: general
0.1.x
Other Linux
: Normal major
: ---
Assigned To: dvb-daemon-maint
dvb-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-21 10:07 UTC by Simon Lanzmich
Modified: 2011-10-06 15:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Simon Lanzmich 2011-09-21 10:07:34 UTC
This happens when the group's recording directory is set to e.g. $HOME, which I picked as a random default that I intended to change afterwards.

RecordingsStore.restore_from_dir() recursively reads the directory's contents, which takes quite some time to finish. As the daemon does not respond to the UI before it's finished, the group is not created (or at least not shown in the UI).
Maybe RecordingReader.restore_from_dir() should not recurse into hidden directories and only up to a certain depth in the tree -- depending on how recordings are usually organized (I did not check this). Further or alternatively, the restore_from_dir() step could be done later and not interfere with initial setup.
I'm running version 0.1.22, but the relevant code does not seem to have changed afterwards.
Comment 1 Sebastian Pölsterl 2011-10-06 15:39:49 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.