OS/2, eCS & ArcaOS - Technical > Web applications
Dooble releases, Qt5 builds
Remy:
--- Quote from: Dave Yeo on April 12, 2025, 06:31:09 am ---
--- Quote from: Remy on April 12, 2025, 02:39:26 am ---Now, tried simplebrowser from QT6.2.11
(I set correct environment and run simplebrowser)
At open time + initial link page load, it took about 30M of shared low storage
I check QT ver and 6.2.11 is displaied
Opened, 2, 3, 4 tabs with link, no shared low memory decrease ! it works
--- End quote ---
Was this with single process?
Here I don't find Dooble-Qt6 keeps using up lower shared memory, it does eat up high shared memory. Also at one point I lowered my VIRTUALADDRESSLIMIT from 3072 to 2944 which cured a lot of the hangs here. Might want to try lowering it depending on what it is set at.
--- End quote ---
I had lower VIRTUALADDRESSLIMITE and I increased it until 2944 for best overall results.
Currently, using 2944.
Dooble.exe --disable-gpu --log-level=1
Dave Yeo:
I meant was the simplebrowser in single process mode to make a better comparision.
--- Code: ---set QTWEBENGINE_CHROMIUM_FLAGS="--single-process" simplebrowser.exe
--- End code ---
You might want to try even lower on the VIRTUALADDRESSLIMIT, perhaps 2560 for a bit.
The potential problem is if PCI address space on your machine is larger then expected.
Remy:
--- Quote from: Dave Yeo on April 12, 2025, 04:58:05 pm ---I meant was the simplebrowser in single process mode to make a better comparision.
--- Code: ---set QTWEBENGINE_CHROMIUM_FLAGS="--single-process" simplebrowser.exe
--- End code ---
You might want to try even lower on the VIRTUALADDRESSLIMIT, perhaps 2560 for a bit.
The potential problem is if PCI address space on your machine is larger then expected.
--- End quote ---
It was at 2560 before I push the value up to 2944 (increased by step and checked if all works as usual before trying next value)
interesting !
- Simplebrowser start in single process mode (free shared low storage decreases as well but less than under Dooble)
- Tried Dooble removing single process mode : free shared low storage is nearly stable, after opening 5 tabs with links, only 30M more shared low storage was taken
(the minus 30M occurs opening third tab or changing link from within tab2 loaded page)
Dooble QT5 has the single process mode on but no problem (free shared memory is stable)
Remy:
Dooble without single process mode is not usable.
When opening web pages, often the page start to load and then, it goes full grey and nothing more...
Back to single process mode but then, free memory issue....
Dave Yeo:
Yes, multi-process mode on OS/2 is broken. It's a shame as single-process mode is only supposed to be used for debugging and it is quite possible that Qt6 is different with how it handles single-process mode.
Did this memory problem start happening with the recent releases or was it there before for you?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version