Hi Pritpal,
Huge effort and very nice job.
I'm worried about one remaining thing: the monolithic
nature of hbqt_slots.cpp. I'm not sure of the meaning of
it, but it seems to contain references to various QT
objects (f.e. even QTWebKit) in one central location.
These object are now implemented in separate libs, and
I wonder if referencing them like this wouldn't cause
pulling of unnecessary parts in final apps?
After testing demoxbp, the Web tab doesn't load all
images, plus it flickers when moving around with the
mouse, sometimes the whole page reappears only when
going above the title bar f.e. Same effect can be
seen in Lists tab with the scrollbars.
Brgds,
Viktor
On 2009 Oct 31, at 19:48, Pritpal Bedi wrote:
Hello Everybody
Here are the results of debug output of demoxbp.exe.
http://old.nabble.com/file/p26144968/2.zip 2.zip
And this is the consolidated result of log file above:
OBJECT Created Released
==============================
QApplication 1 => 1
QWidget 9 => 9
QVariant 1 => 1
QEventLoop 1 => 1
QSize -- => 2
QDesktopWidget 1 => 1
QColor 33 => 33
QMenuBar 1 => 1
QMenu 4 => 4
QAction 12 => 12
QKeySequence 2 => 2
QStatusBar 1 => 1
QPixmap 3 => 9
QCursor 5 => 5
QToolBar 1 => 1
QTabWidget 1 => 1
QFrame 16 => 16
QScrollBar 4 => 4
QHeaderView 3 => 3
QGridLayout 1 => 1
QFontMetrics 12 => 12
QFont -- => 12
QTextEdit 2 => 2
QCheckBox 4 => 4
QRadioButton 4 => 4
QSpinBox 3 => 3
QTreeWidget 2 => 2
QTreeWidgetItem 99 => 100 ( 220-417 == 98 Items )
QTreeWidgetItem 99 => 100 ( 422-619 == 98 Items )
QListView 2 => 2
QStringList 2 => 2
QStringListModel 2 => 2
QLineEdit 3 => 3
QComboBox 1 => 1
QPushButton 15 => 15
QTextCursor -- => 7
QTextCharFormat -- => 9
QBrush 2 => 4
QWebView 1 => 1
QUrl 1 => 1
QGroupBox 1 => 1
QLabel 7 => 7
QImage 1 => 1
QIcon -- => 1
QPoint 1 => 1
QModelIndex -- => 6
hbqt_ptrTOgcpointer 46 => --
-- 37
QPixmap 6
QBrush 2 45
It is one-to-one means whatever objects appln is creating with
new Q() or creating dynamically is being released properly.
But still 1.3 MB of memory is never reclaimed with next invocation
of "One More Dialog". Application reclaims 1.7 MB but cannot reclaim
1.3 MB.
If we look at the zipped 2.log file, we can see that at system
level no memory is released though Harbours internal items gets
released.
Only at the end of the Main() function system releases 1.7 MB.
Any ideas what could be points to see through or debug more.
It is verified that Qt level delete ( Q* ) ph ; is executed as
intended and
object is releases but system memory stays the same.
This is the only issue left with Harbour-Qt. Once we resolve it we are
through.
Note that before introducing collectible pointers not even a single
byte
was being reclaimed. Now at least we are able to get back more than
half
of memory.
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/HBQT---HBXBP---Releaseing-the-Objects-and-Memory-tp26144968p26144968.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
