QObject::dumpObjectTree against a suspect object will reveal if it's accumulating "trash". Run it against QApplication while doing repeated scroll windows or WebKit calls and you'll find plenty. (Supposedly fixed in 4.7 beta 2.)
<scoll area ptr>->viewport()->ungrabGesture(Qt::PanGesture);
will clean up some of the leaks, when done after one of these: QAbstractScrollArea, QScrollArea, QPlainTextEdit, QTextEdit, QTextBrowser
In general you can track heap growth on Symbian with something like this:
Code:
void HeapLeak::updateHeapStats() {
#ifdef Q_OS_SYMBIAN
TInt mem, size, limit;
User::Heap().AllocSize(mem);
size = User::Heap().Size();
limit = User::Heap().MaxLength();
#endif
ui.countLabel ->setText(QString::number(count));
ui.countLabel ->update();
#ifdef Q_OS_SYMBIAN
ui.memLabel ->setText(QString::number(mem));
ui.memLabel ->update();
ui.sizeLabel ->setText(QString::number(size));
ui.sizeLabel ->update();
ui.limitLabel ->setText(QString::number(limit));
ui.limitLabel ->update();
#endif
}