| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I2ba997eac9d3ff75542b5861dbbc89d3ccd6017e
Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: If583799f3dfd09c6c5c49ee8305c0df8b038881a
Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Id77917c92191d3970727be0b360abefc87254c5b
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
It seems those were forgotten when the scene graph profiler was
refactored.
Change-Id: I4cf5f1cae701ec4ff64659bd023fb5941715e7e1
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: Ifae1ac725518d1a7fb12b46bd36485cd46ebf082
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: Id24ca60a8166394811e0ff93f5bd1d3e198ac67e
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
It shouldn't display 0-size timings and it should distinguish the
threads more clearly. Also, we display the gross render time in
addition to the render time breakdown. This seems to be rather
important information for users.
Change-Id: I3c1d94f1489902a815c20831e8e1059c815ef129
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: I09e9481296cbd0429858df893de902c63891b430
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: Id28186a5e24c9b0f6f89142ba4c35d1a5a462852
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
|
|
| |
This helps if you have multiple pixmaps with equal names.
Change-Id: I39a16f55d16c5729483c037b8c125795105fae0a
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
plugins/qmlprofilerextension/qmlprofilerextensionplugin.cpp
Change-Id: Ied74b2e97a51bd5ee67864e6dd5c830d57ea3099
|
| |
| |
| |
| |
| |
| |
| | |
This requires http://qt-gerrit.it.local/#change,6220 in licensechecker.git
Change-Id: Ia7bc7bcee90d3099805a43106f1f0b695bbf059b
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I96a40813ad8aebcb86ddc9ed08327fe836681267
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I1c31d5463ae39b988c7a0ffb4168a952e53c152c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I6e159702e533848c9eb9c98551743d5472f2155c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
Also add a stub input events model to represent that feature.
Change-Id: Idd05b9452b7c6920779e72966ce62c0a1decaeef
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I3fb0d91dafbb42b0422263b6710b1a0fcb4c193c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
It means the same but is shorter and doesn't get elided.
Change-Id: I0ef221bb844691b9c15a3c10743bfd7389fe95ae
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ib396f4a28ddcfc5a4d95beb4a22dbd109d06b38e
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ifef5ac0b3ffa05b17d6f17adf8a8c2f745a98e1c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I31c8eea2b9e21247e83ef0e5d23b0b568b1f177c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ie028a6b1e5e2e01acba235f76aa431a9875fa984
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I0e5da4f829be1d94a32b73a6383e0ddf5c69dd33
Reviewed-by: Andre Poenitz <andre.poenitz@digia.com>
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I432e334cee3cfc97970224c0f61213dc4f0a2cc2
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The scene graph profiler was pretty barren. The ranges it showed were
only vaguely related to actual events and the numbers shown in the
labels weren't really informative.
This change shows every stage in GUI thread and rendering thread as its
own range, so that you can easily see now if a particular stage takes
unusually long. This comes at a cost, though: The color is used for
showing event types instead of frame rates now and there is no 1:1
mapping of rows to threads anymore. The first row is still reserved
for the GUI thread and the second one for the render thread. Further
rows are used as needed, though, and you can meaningfully expand the
category now.
Task-number: QTBUG-39876
Change-Id: Ib91ba454dd0e3e7482ca2afe6d3c80d9868bcce3
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Adapt to the new signature of the details method and don't create
unnecessary nested maps.
Change-Id: Iab8d31e48d35923fee3e258c0390459a81ece746
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I470bcaaf53a6184ae35369484337b247bf17f52e
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ic26122d319dd56a4666a02bf6979c292581473ea
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I7747ea5f8485795ad7777fa2f411afcff01956f8
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: Ifa2b9350ed68b42a04f589368492d318548dc7e2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The memory profiler aggregates allocations originating from the same
QML/JS constructs into one event. This change makes sure the origins
are really the same calls, not only the same functions and gives some
more details on hom much memory was allocated or deallocated in how
many steps.
Change-Id: I784c521855122f7b3b894417de0afb216766e2d4
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ief0b14ae2be15bf5e9db31d8f6625882a17f685a
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
For delta < 0 it's "freed", not "allocated
Change-Id: I1ac400588329152f70d63a2ec4a0498c6f54d299
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: I15f9db0dd9d65ceaff9503c535abd7abcbd1eccc
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The indices SortedTimelineModel returns are only valid until you insert
something at a different place than the end. If you do that, all later
events are shifted by one. We can "fix" that by also shifting the saved
indices.
Change-Id: I63180dabea0c52db55e799b023b3f2bf84f9e59a
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
lastTimeMark is just the end of the last recorded event. The memory
will still be allocated after that.
Change-Id: Ica12993d7b1572c145bba6373461240a5e846fa9
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: I1a26f3e2fb838df2d3df1784d6a8ea65fbcf4418
|
| |
| |
| |
| |
| |
| |
| |
| | |
By showing the same numbers with units in the labels we avoid leading
people to assume bytes as unit.
Change-Id: I56d2ca5f21434fd24a305aebd434371438da7ebb
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|\ \
| |/
| |
| | |
Change-Id: I920aa7056923a994c7d54ac31e32b45fcca84394
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-39876
Change-Id: I01c15ede43a9d94fdfc3123b6df8a235430cfc81
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Id33fa51daffe97e9e60467942b92f0598a17c27d
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I69cb67a97b0bb3407f509db01ec2d4b9acd177db
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
There is no point in showing a displayName that's the same as the
description.
Change-Id: Ie6ace79e622e31b87ff42d741e04103a920b36e4
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If no polishAndSync event is ever seen we can be sure the application
is doing non-threaded rendering. In that case all other events belong
to the GUI thread rather than the render thread.
Change-Id: Ib5d0cbcdc7c45bff6303a1b4bfb1f5333830c7f7
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|/
|
|
|
|
|
| |
So they can be set through .qmake.conf in a subdirs project above it.
Change-Id: I919e637fb7ed8a7f341982f0a9f06953e0131a2a
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
|
|
|
|
|
| |
Change-Id: Ie2ad2f7ab326adb88334b3bd686cbde0f25f1a83
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: I720f067956417519e58fac9d92292edd7968356d
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
|
|
|
| |
An additional model to represent memory usage of the application being
profiled.
Change-Id: I5f1e1e06a31adf2e4ba0bb63147492b6b5f50a3e
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: I0af479f2405a9c71602b9635e8e8ec4b1bcb9554
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
| |
Change-Id: If105f490a02ffabe07d2b4871c655972445c6a19
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|