Comment 27 for bug 251128

Yes, this crash on exit still happens on my i965 chipset in Linux as
well. I have tried to chase it down before, to no avail. I first thought
that the ~30 fps timer was re-entering the QGLWidget's event handler
after it had been destroyed, but I turned off the timer code and was
still able to cause the crash. I also tried deleting it via deleteLater,
as the docs suggest for deleting a QObject which may have pending events
in the GUI event loop. When I get my backtrace, I see that the QGLWidget
is being deleted via deleteChildren of MixxxView. I also tried using
deleteLater on MixxxView, and this doesn't seem to work either. I can't
think of any other way to delete the thing, and it doesn't look like it
has some sort of 'shutdown' method that should be called before deleting
it.

-RJ

Albert Santoni wrote:
> This is the first time we've ever been able to see a real backtrace
> for one of these mystery Win32 crashes. This is great, thanks holgers!
>
> It seems to be dying in some driver-provided OpenGL function or
> something. I wonder if we need to destroy our QGLWidgets (the waveform
> views) in a nicer way (or maybe that's where it's dying?)...
>
> Ideas?
>
> On Thu, Mar 26, 2009 at 11:15 AM, holgers <email address hidden> wrote:
>
>> Wasn't sure how to copy/paste information from the debugger so I just
>> took a screenshot which I've attached.
>>
>> ** Attachment added: "backtrace.jpg"
>> http://launchpadlibrarian.net/24369100/backtrace.jpg
>>
>> --
>> Runtime error on exit
>> https://bugs.launchpad.net/bugs/251128
>> You received this bug notification because you are a member of Mixxx
>> Development Team, which is subscribed to Mixxx.
>>
>>
>
>