Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.4.0
-
None
-
1de6e7b8e0ee465f642e1b2f5a14611e52a7e8c2
Description
Profiling the QML Profiler in an old QtCreators painting the timeline overview for some seconds gives me a 1.3G trace file with almost only memory allocation events. It also takes forever to transfer the data. We need a way to limit this, at least optionally.
Maybe we should just stop collecting events after a certain threshold has been surpassed; the threshold could be configured with an additional command line parameter.
Attachments
For Gerrit Dashboard: QTBUG-41118 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
93942,2 | Select specific features to be recorded when profiling QML | dev | qt/qtdeclarative | Status: ABANDONED | 0 | 0 |
94319,3 | Select specific features to be recorded when profiling QML | 5.4 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
94361,5 | QmlProfiler: Allow preselection of events to be recorded | master | qt-creator/qt-creator | Status: MERGED | +2 | 0 |
94408,4 | QmlProfiler: Filter event types also on client side | master | qt-creator/qt-creator | Status: MERGED | +2 | 0 |