[Development] leak in QMetaObject?
thomas.senyk at pelagicore.com
Thu Jul 14 19:08:11 CEST 2016
On 14.07.2016 18:56, Thiago Macieira wrote:
> On quinta-feira, 14 de julho de 2016 18:37:17 PDT Thomas Senyk wrote:
>> On 14.07.2016 18:25, Thiago Macieira wrote:
>>> On quinta-feira, 14 de julho de 2016 17:45:58 PDT Thomas Senyk wrote:
>>>> should "fix" it? .. but I still see 100% cpu and same memory consumption?
>>> Can you attach the debugger to see what it is still doing after you're
>> Still the same, goes in circles around in QMetaObject::activate
>> #3671 => #3673 => if (!c->receiver) continue => while => ...
>> ... pressing F10 for a while doesn't let you out of that (short) cycle.
>> If you want to know (I know it's not saying much) the values for
>> list->first and list->last: @0x1529ac0, @0x6a3a3250
>> Is that what you wanted to know? If I misunderstood, please clarify :)
> I wanted a backtrace. Are you saying the trace is 3700 frames deep?
Sorry that was line numbers :) No it's not.
About to generate a callgrind output.
More information about the Development