Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fseek]

For some time now I've been getting the following errors:

Code: [Select]

(amule:4133): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' failed

(amule:4133): Gtk-CRITICAL **: gtk_pixmap_set: assertion `gdk_colormap_get_visual (gtk_widget_get_colormap (GTK_WIDGET (pixmap)))->depth == gdk_drawable_get_depth (GDK_DRAWABLE (val))' failed

I think the errors are related to the statistics and kad charts because I've seen them occurring when the carts get updated.

This problem started occurring after an upgrade of either the gtk2 or the wxgtk libs (from the pkgsrc of netbsd 3.0). Normally I wouldn't mind, but the error seems to be the cause of a memleak in the X server: after an hour or two the X server kills amule with the following error message:

Code: [Select]

The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 82790081 error_code 9 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

At this point, if I try to restart amule it immediately gets killed. The only way to have amule to run again is to restart the X server.

When the error occurs the RSS of the X server is around 128MB (which I think is the default current limit for the user).

Now the question: amule or bug?  :rolleyes:

Thanks

[Xaignar]

It is possibly a bug in your GTK theme.