[Pkg-xfce-devel] Bug#440848: Bug#440848: xfce menu terminating unexpectedly
On Tue, Sep 04, 2007 at 09:45:44PM +0200, Alexander Toresson wrote:
> On 9/4/07, Yann Dirson <ydirson at altern.org> wrote:
> > Package: xfdesktop4
> > Version: 4.4.1-5
> > Severity: important
> > Twice in the last days, the "xfce menu" plugin was not there any more
> > after unlocking the screen. My .xsession-errors has 2 occurences of
> > the following lines. I have only started to use xfce a short time
> > ago, so I can't tell if that's a recent issue.
> > | ** Message: Xfce Menu: screen changed: 0
> > |
> > | ** Message: No valid plug window.
> > |
> > | (xfce4-panel:15761): Gtk-CRITICAL **: gtk_socket_get_id: assertion `GTK_WIDGET_ANCHORED (socket)' failed
> > |
> > | ** (xfce4-panel:15761): CRITICAL **: An item was unexpectedly removed: "Xfce Menu".
> I bet this is due to it leaking memory and thus eventually crashing.
> It would be nice if you could verify that or at least measure the
> memory usage of the menu plugin after a few hours, though.
Right, digging the logs I find the OOM triggered too often those last
days. And the process currently looks like:
0 1000 24983 15761 18 0 1387760 819188 47278 S ? 15:32 /usr/lib/xfce4/panel-plugins/xfce4-menu-plugin socket_id 16222881 name xfce4-menu id 11891817573 display_name Xfce Men
Restarting it it gets suddenly more reasonable:
0 1000 10461 15761 15 0 18048 12508 47278 S ? 0:01 /usr/lib/xfce4/panel-plugins/xfce4-menu-plugin socket_id 16447914 name xfce4-menu id 11892828144 display_name Xfce Men
> If you then would like to be really ambitious, you could try to
> provide us with a valgrind log of the leak for us to pass to upstream.
I'll try to find some time to do that in the next days.