aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUlf Hermann <ulf.hermann@theqtcompany.com>2014-11-20 11:04:42 +0100
committerUlf Hermann <ulf.hermann@theqtcompany.com>2014-11-24 19:35:49 +0200
commitd8210098225155817fc58b3e82d899f7856a8c7a (patch)
tree500a18f213693535b0f1d3c72f735d88d2384562
parent6438cacf1ad414a85a7786004c510a2bd9a1a116 (diff)
Properly initialize max size in memory usage model
Change-Id: Id77917c92191d3970727be0b360abefc87254c5b Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
-rw-r--r--plugins/qmlprofilerextension/memoryusagemodel.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/plugins/qmlprofilerextension/memoryusagemodel.cpp b/plugins/qmlprofilerextension/memoryusagemodel.cpp
index e61ee36683..5a83899cd7 100644
--- a/plugins/qmlprofilerextension/memoryusagemodel.cpp
+++ b/plugins/qmlprofilerextension/memoryusagemodel.cpp
@@ -44,6 +44,8 @@ MemoryUsageModel::MemoryUsageModel(QObject *parent)
tr(QmlProfilerModelManager::featureName(QmlDebug::ProfileMemory)),
QmlDebug::MemoryAllocation, QmlDebug::MaximumRangeType, parent)
{
+ Q_D(MemoryUsageModel);
+ d->maxSize = 1;
}
quint64 MemoryUsageModel::features() const