434750f1a6
As the various file names are actually not kept as QStrings in the respective objects being profiled, our saving them as QStrings in each and every profiling event is not implicitly shared and causes a huge memory overhead. Avoid that by saving each location only once, indexed by a disguised pointer to the object it refers to. Normally, objects could disappear during the profiling session, and new objects could be allocated in their place, which would mess up our indexing system. We prevent that by referencing the objects when we index them, thus preventing them from getting auto-destructed. Mind that those are not JavaScript objects but rather functions, bindings, components and the like. So, this will only cause a memory leak if you're compiling and dropping QML components over and over. Task-number: QTBUG-52937 Change-Id: Ia4dfb09a71a5c9a2d6ce25c3811bbe2a1036c1c1 Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com> |
||
|---|---|---|
| .. | ||
| animations | ||
| compiler | ||
| debugger | ||
| doc | ||
| jit | ||
| jsapi | ||
| jsruntime | ||
| memory | ||
| parser | ||
| qml | ||
| types | ||
| util | ||
| Qt5QmlConfigExtras.cmake.in | ||
| qml.pro | ||
| qtqmlglobal.h | ||
| qtqmlglobal_p.h | ||