Sebastien, can you please attach the full backtrace (bt full) from your own debug build?
Ichudov, yes this is a relative new feature and it exposes old and new bugs in the system that were not exercised before. I hope it will quickly improve. Your testing and bug reports are very valuable. >From what I can see, in I830LeaveVT() pI830.gen4_render_state is 0x994ed80 which sounds like a reasonable pointer, but when it gets down to gen4_render_state_cleanup() what should have been the same pointer is now 0xc which sounds corrupted. You can verify this by printing out *pI830 from frame 11 as well. If you are experienced with gdb, you can set a watchpoint on this data location to see when it is being overwritten. But anyway I think we can forward this upstream. Maybe they will understand what goes wrong without digging further with gdb. Sebastien, which line of code does it crash (use the "list" command in gdb). The trace says line 1727 but I can not be sure that is the same as in my source. If it does not crash in the first unreference, I am a bit surprised. You can also print *pI830->gen4_render_state in both frame 11 and 12. Or set a breakpoint and check it before it is calling gen4_render_state_cleanup(). Argh, remote gdb debugging via a bug tracker is just frustrating :) -- Swithing to another user and then to anything else, freezes laptop. Jaunty https://bugs.launchpad.net/bugs/348428 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
