Hello; I've been tracing a bug in my code that calls 'clutter_actor_destroy'. For some reason bad things happen and I managed to trace it as possible bug in fglrx driver (?) (see backtrace below) However, this brings the question that if I want to destroy an clutter_texture actor, why would I want to read pixels from graphics card to main memory? This happens in clutter_texture_unrealize. I want to get rid of the actor and all memory it has, the pixelreading there is a lot of overload.
---------- 8< --------------------------------------------------------- (gdb) bt #0 0xb7a12cbc in memcpy () from /lib/tls/i686/cmov/libc.so.6 #1 0xb798544c in __glEmptyImage () from /usr/lib/libGL.so.1 #2 0xb798bd89 in __indirect_glGetTexImage () from /usr/lib/libGL.so.1 #3 0xb7f6f6af in clutter_texture_get_pixbuf (texture=0x806b130) at clutter-texture.c:1149 #4 0xb7f6ffcc in clutter_texture_unrealize (actor=0x806b130) at clutter-texture.c:645 #5 0xb7f41d84 in clutter_actor_unrealize (self=0xc0000) at clutter-actor.c:452 #6 0xb7f4428b in clutter_actor_unparent (self=0x806b130) at clutter-actor.c:3672 #7 0xb7f5aa87 in clutter_group_real_remove (container=0x8062058, actor=0x806b130) at clutter-group.c:265 #8 0xb7f53f34 in clutter_container_remove_actor (container=0x8062058, actor=0x806b130) at clutter-container.c:296 #9 0xb7f449e3 in clutter_actor_destroy (self=0x806b130) at clutter-actor.c:2040 #10 0x08049716 in input_cb (stage=0x8062058, event=0x805e230, data=0x0) at test.c:72 // Tapani Pälli -- Software Engineer Open Source Software Operations -- To unsubscribe send a mail to [EMAIL PROTECTED]
