Bug#525031: gnome-settings-daemon: spins on cpu, possibly while Registering GsdXrandrPlugin

[dann frazier]

found 525031 2.26.1-2
thanks

On Fri, Aug 14, 2009 at 11:48:59AM +0200, Josselin Mouette wrote:
> Le mercredi 29 avril 2009 à 16:46 -0600, dann frazier a écrit :
> > 0x2000000002855150 in register_gnome_settings_plugin (
> >     module=0x2000000002859020) at gsd-xrandr-plugin.c:36
> > 36  GNOME_SETTINGS_PLUGIN_REGISTER (GsdXrandrPlugin, gsd_xrandr_plugin)
> > (gdb) bt full
> > #0  0x2000000002855150 in register_gnome_settings_plugin (
> >     module=0x2000000002859020) at gsd-xrandr-plugin.c:36
> >     our_info = {class_size = 152, base_init = 0, base_finalize = 0, 
> >   class_init = 0x2000000002816ba0, class_finalize = 0, class_data = 0x0, 
> >   instance_size = 32, n_preallocs = 0, instance_init = 0x2000000002816bb0, 
> >   value_table = 0x0}
> > #1  0x2000000002855140 in register_gnome_settings_plugin (
> >     module=0x60000000000605e0) at gsd-xrandr-plugin.c:36
> >     our_info = {class_size = 152, base_init = 0, base_finalize = 0, 
> >   class_init = 0x2000000002816ba0, class_finalize = 0, class_data = 0x0, 
> >   instance_size = 32, n_preallocs = 0, instance_init = 0x2000000002816bb0, 
> >   value_table = 0x0}
> > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> 
> Sorry for the delay, I have a huge backlog.
> 
> I have no idea of what could go wrong in this code, but at least it
> explains why this happens for several plugins.
> 
> Does it still happen with gnome-settings-daemon 2.26 ? No relevant code
> seems to have changed, but this may be triggered by funky side effects.

It is still occuring with 2.26.1-2.

-- 
dann frazier