[Development] Proposal for "container-oriented deterministic memory manager"

Phil Bouchard philippeb8 at gmail.com
Thu Dec 29 14:49:24 CET 2016

On 12/29/2016 04:14 AM, Simon Hausmann wrote:
> Hi,
> I don't doubt that root_ptr can be used at all. What I'm curious about
> is what your thoughts are on how it could perform, how you would map its
> strengths to the allocation patterns of QML binding evaluations and
> general ECMAScript code.

I'll need to have a general overview of the ECMAScript and study it 
further before speculating.  My knowledge of Javascript is not at the 
expert level yet so any pointers are appreciated.

> For the record: Any animation code that _doesn't_ use QML Animators does
> indeed run in the same thread as the STW garbage collector and is
> therefore subject to its non-deterministic behavior (from the animation
> PoV). QML Animators on the other hand are run entirely in the render
> thread and are not affected by any pauses in the gui thread, whether it
> is caused by long running scripts, the garbage collector or
> blocking disk I/O. If with today's release you want to have guaranteed
> lag-free animations, then the use of animators over NumberAnimation,
> etc. is required. That is why it _is_ possible to run smooth animations
> with the scene graph and QML on crazy high resolution displays at
> minimal CPU usage.
> That said, it is our expressed goal to improve the garbage collector to
> interrupt the GUI thread as little as possible, because not everything
> can (and should) be solved with animators. Scrolling in a listview,
> delegate re-use, property re-bindings, etc. are things that still have
> to run in under 16 ms. So without any doubt there is work to do ��

I'll do my best to help but one again am I not yet an advanced 
Javascript programmer but I'm sure architects understand this stuff like 
the back of their hand.

So please give me some time to study this as this week I have skiing 
training sessions to give to kids.

More information about the Development mailing list