GLib-GObject-CRITICAL

[Jaime Pérez]

screen blinks or something like that and i get error

(anjuta:30976): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(anjuta:30976): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-0 2.40.2-0ubuntu1
Uname: Linux 3.18.0-031800-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Dec 9 21:08:48 2014
InstallationDate: Installed on 2014-12-01 (8 days ago)
InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (20141111)
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

[Jaime Pérez (jaime-91)]

(anjuta:30976): Gdk-ERROR **: The program 'anjuta' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 7320544 error_code 16 request_code 18 (core protocol) 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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

[Jaime Pérez (jaime-91)]

I put the error in an atachment

[Jaime Pérez (jaime-91)]

Some info in dmesg too

[Toan (tpham3783)]

I compile glib library from source and I learn that if optimization (-Os -O1 or -O2) was turned on during compilation, particularly when compiling gobject/gobject.c from glib, can lead to many strange behaviors and errors.

If for somehow, you can try to recompile glib without optimation and see if the error goes away. thanks

TP