[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [Bug 312280] amarok locks up when saving edited track details
From:       robert marshall <robert () capuchin ! co ! uk>
Date:       2012-12-30 19:05:54
Message-ID: bug-312280-71684-liDOnBwJht () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=312280

--- Comment #6 from robert marshall <robert@capuchin.co.uk> ---
I've put a breakpoint in TagDialog::~TagDialog (the destructor) and am seeing
it being called twice on exit from the dialog, is this to be expected? it feels
wrong (esp thinking of the message I got - double free - in comment #1)
Breakpoint 1, TagDialog::~TagDialog (this=0xa7124d0, __in_chrg=<optimised out>)
    at ../../src/dialogs/TagDialog.cpp:117
117    in ../../src/dialogs/TagDialog.cpp
(gdb) c
Continuing.
[0x99edf80] main input error: ES_OUT_SET_(GROUP_)PCR  is called too late
(pts_delay increased to 300 ms)
[0x99edf80] main input error: ES_OUT_RESET_PCR called

Breakpoint 1, TagDialog::~TagDialog (this=0xa7124d0, __in_chrg=<optimised out>)
    at ../../src/dialogs/TagDialog.cpp:117
117     in ../../src/dialogs/TagDialog.cpp

is the same item being deleted twice, would a backtrace at those points be
helpful? (though the deletion appears to be called from the inside of Qt) This
was a call on 'edit track details' which didn't cause a lockup - from #5 it
looks as if the destructor doesn't get called in the cases where it does
lockup.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist
[prev in list] [next in list] [prev in thread] [next in thread]