Author Topic: Qt6 Application Testing  (Read 420873 times)

David McKenna

  • Hero Member
  • *****
  • Posts: 889
  • Karma: +32/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #855 on: May 08, 2025, 12:20:38 am »
Hey Paul,

  I get the same result as you, but I also have my RPM environment totally current. I was able to get it to work by just copying QT6WebEn.dll from your last package (20250505) to the new one and then it all worked.

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2530
  • Karma: +193/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #856 on: May 08, 2025, 01:14:33 am »
Bugger....I guess something in gcc 15 is triggering this. Will investigate over the next few days. On the plus side, I didn't get any out of memory failures building with 2 jobs.

FWIW sample exceptq.txt attached.

Lookingback through my emails, this seems to be an alignment issue - the joys of our aout object format......

Thankfully, it seems I fixed this in the Qt 6.4.x code with https://github.com/psmedley/qt6-webengine-os2/commit/d2b464fdc27bf23b1891ba63c1f5c00cd5b7a88c I knew the trp looked familiar....

Yep, with https://smedley.id.au/tmp/qt6-6.2.12-qtwebengine-6.2.6-os2-20250508.zip at least os2world.com loads ok :)
« Last Edit: May 08, 2025, 11:15:11 am by Paul Smedley »

David McKenna

  • Hero Member
  • *****
  • Posts: 889
  • Karma: +32/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #857 on: May 08, 2025, 12:58:40 pm »
Paul,

 Yes, this one seems to work as well as the previous working version - with the same limitations (mostly occasional random system hangs). Any thought on trying to build the 6.2.12 version of webengine?

Regards,

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5404
  • Karma: +128/-1
    • View Profile
Re: Qt6 Application Testing
« Reply #858 on: May 08, 2025, 06:01:48 pm »
What I'm wondering is whether there is an equivalent Qt5 Webengine to 6.2.6 and how to merge it.
Trying to clone Qt5 from the official sources, init repository fails,
Code: [Select]
H:\tmp\qt5>sh init-repository
init-repository: 35: init-repository: use: not found
init-repository: 36: init-repository: use: not found
init-repository: 37: init-repository: use: not found
init-repository: 39: init-repository: package: not found
init-repository: 42: init-repository: Syntax error: "(" unexpected

H:\tmp\qt5>bash init-repository
init-repository: line 35: use: command not found
init-repository: line 36: use: command not found
init-repository: line 37: use: command not found
init-repository: line 39: package: command not found
init-repository: line 42: syntax error near unexpected token `('
init-repository: line 42: `sub printUsage($)'

Have to look closer after work.

Steven Levine

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +12/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #859 on: May 08, 2025, 07:19:50 pm »
init-repository is a perl script.  It appears something is going wrong with hash-bang processing on your setup.

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2530
  • Karma: +193/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #860 on: May 08, 2025, 10:45:17 pm »
Yes, this one seems to work as well as the previous working version - with the same limitations (mostly occasional random system hangs). Any thought on trying to build the 6.2.12 version of webengine?

I'm currently stuck on 6.2.8 - which is the same webengine that came as part of Qt 6.4.x. The code compiles, but pretty much any site with javascript crashes. Any newer than 6.2.8 and we hit the webengine that came with Qt 6.5 - and we encounter https://github.com/bitwiseworks/node-os2/issues/1 where Dmik and I both got stuck at basically the same crash.

So in short, No.

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2530
  • Karma: +193/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #861 on: May 08, 2025, 10:50:14 pm »
What I'm wondering is whether there is an equivalent Qt5 Webengine to 6.2.6 and how to merge it.
Trying to clone Qt5 from the official sources, init repository fails,

In short....
Qt 6.2.6 - https://github.com/psmedley/qt6-webengine-os2/blob/main/CHROMIUM_VERSION
Code: [Select]
Based on Chromium version:                                      94.0.4606.126
Patched with security patches up to Chromium version:           104.0.5112.81

Qt 5.15.19 (latest tag at https://github.com/qt/qtwebengine/blob/5.15.19/CHROMIUM_VERSION
Code: [Select]
Based on Chromium version:                                      87.0.4280.144
Patched with security patches up to Chromium version:           135.0.7049.95

So the latest 5.15 version is older than what we have. We could however, try and cherry-pick the security fixes.
« Last Edit: May 09, 2025, 08:48:07 am by Paul Smedley »

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5404
  • Karma: +128/-1
    • View Profile
Re: Qt6 Application Testing
« Reply #862 on: May 11, 2025, 09:02:46 pm »
There's something seriously wrong with code pages and perhaps icu. Using dooble-qt6, simply opening it, displaying the release notes and closing it results in this,
Code: [Select]
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1987 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KSC_5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias 5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias windows-949 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1989 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias csKSC56011987 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias korean maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias iso-ir-149 maps to cp1363 already, but someone is trying to make it map to EUC-KR

As far as I can see, the release notes are straight ASCII.
I've also seen errors related to ICU.
For Mozilla, had to re-add cp850 at one point when they cleaned up the codepage section.
Doing the same with dooble-qt5 results in no messages to stdout/stderr
Another observation is here, going to github often sees dooble-qt6 close pretty quick. Redirecting stdout/stderr (dooble 2>&1 | tee dooble.log) sees dooble display the pages. Timing issue I assume.

David McKenna

  • Hero Member
  • *****
  • Posts: 889
  • Karma: +32/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #863 on: May 11, 2025, 10:02:45 pm »
Dave,

  I see quick hangs or closes in Dooble QT6 with github too. Just thought it was because of the age of our WebEngine, but maybe not?

Regards,

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5404
  • Karma: +128/-1
    • View Profile
Re: Qt6 Application Testing
« Reply #864 on: May 11, 2025, 10:14:06 pm »
Try running "dooble 2>&1 | tee dooble.log"
Unluckily github has changed its code again and even dooble-qt6 is choking on various stuff. Filed an issue yesterday, https://github.com/textbrowser/dooble/issues/261 and had to use my phone to do the initial post. Luckily can continue the conversation with email.

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2530
  • Karma: +193/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #865 on: May 12, 2025, 10:04:10 am »
There's something seriously wrong with code pages and perhaps icu. Using dooble-qt6, simply opening it, displaying the release notes and closing it results in this,
Code: [Select]
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1987 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KSC_5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias 5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias windows-949 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1989 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias csKSC56011987 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias korean maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias iso-ir-149 maps to cp1363 already, but someone is trying to make it map to EUC-KR

As far as I can see, the release notes are straight ASCII.
I've also seen errors related to ICU.
For Mozilla, had to re-add cp850 at one point when they cleaned up the codepage section.
Doing the same with dooble-qt5 results in no messages to stdout/stderr
Another observation is here, going to github often sees dooble-qt6 close pretty quick. Redirecting stdout/stderr (dooble 2>&1 | tee dooble.log) sees dooble display the pages. Timing issue I assume.

Is this a new problem with the latest build or ???

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5404
  • Karma: +128/-1
    • View Profile
Re: Qt6 Application Testing
« Reply #866 on: May 12, 2025, 04:46:45 pm »
I think it is an old problem.

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2530
  • Karma: +193/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #867 on: May 12, 2025, 10:56:59 pm »
I think it is an old problem.
Phew! Can you describe how to reproduce?

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5404
  • Karma: +128/-1
    • View Profile
Re: Qt6 Application Testing
« Reply #868 on: May 13, 2025, 01:02:22 am »
I think it is an old problem.
Phew! Can you describe how to reproduce?

Code: [Select]
dooble 2>&1 | tee dooble.log

and go to help-->Release Notes
and then close dooble

David McKenna

  • Hero Member
  • *****
  • Posts: 889
  • Karma: +32/-0
    • View Profile
Re: Qt6 Application Testing
« Reply #869 on: May 14, 2025, 01:57:01 am »
Hey Dave,

  I don't see what you show - when I open Dooble for QT6 and view the release notes, then close all I get is 2 identical lines:

[179:1:0513/195224.972000:ERROR:system_network_context_manager.cpp(299)] Cannot use V8 Proxy resolver in single process mode.
[179:1:0513/195224.979000:ERROR:system_network_context_manager.cpp(299)] Cannot use V8 Proxy resolver in single process mode.

and that's it...

Regards,