Comment 2 for bug 150471

Daniel Hahler (blueyed) wrote :

I think I've seen this bug just happening here, while trying to reproduce bug 148781 and bug 150454. Therefor I've started a new gnome session and when exiting from there I've noticed that nautilus was using all available CPU cycles.

nautilus-debug-log.txt keeps growing, but only with the same "debug log dumped" line:
===== BEGIN MILESTONES =====
0x8177888 2007/10/09 23:16:40.8978 (GLog): Can not calculate _NET_NUMBER_OF_DESKTOPS
0x8177888 2007/10/09 23:16:40.8979 (GLog): Can not calculate _NET_NUMBER_OF_DESKTOPS
0x8177888 2007/10/09 23:16:40.8979 (GLog): Can not get _NET_WORKAREA
0x8177888 2007/10/09 23:16:40.8980 (GLog): Can not determine workarea, guessing at layout
0x8177888 2007/10/09 23:23:20.6097 (USER): debug log dumped due to signal 11
0x8177888 2007/10/09 23:23:20.6246 (USER): debug log dumped due to signal 11
0x8177888 2007/10/09 23:23:20.6247 (USER): debug log dumped due to signal 11
0x8177888 2007/10/09 23:23:20.6248 (USER): debug log dumped due to signal 11
0x8177888 2007/10/09 23:23:20.6250 (USER): debug log dumped due to signal 11
[...]
0x8177888 2007/10/09 23:23:56.0296 (USER): debug log dumped due to signal 11
0x8177888 2007/10/09 23:23:56.0356 (USER): debug log dumped due to signal 11