[Interest] Poor QMethod::invoke performance across threads on i.MX53
Thiago Macieira
thiago.macieira at intel.com
Thu May 28 20:05:45 CEST 2015
On Thursday 28 May 2015 11:28:53 Matthew Woehlke wrote:
> I create an object in Thread 1 (e.g. the main thread). This object is
> memory-owned by T1, i.e. it is expected that T1 will delete the object.
This is what's wrong. T1 *cannot* delete the object that represents T1. If T1
is trying to delete it, then T1 is running and you have a deadlock.
And you can't have another thread delete it unless you move the object to that
thread first.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest
mailing list