OS/2, eCS & ArcaOS - Technical > Programming

Qt6 Application Testing

<< < (176/177) > >>

Jochen Schäfer:
And, please don't forget to package translations.

Martin Iturbide:
Hello

According to other thread it seems a bad idea to try to go "mainstream" (put it on the RPM) with Qt 6.8.1 at the moment.
Maybe we should start with 6.2.6 and wait if there are some progress with versions 6.7 or 6.8.

Qt also has LTS (Long-Term Support releases) versions, It seems that Qt 6.5.x(LTS) is the one will hold to 2026-03-30, then it cames Qt 6.8.x to 2029.

Regards

Remy:
Hi !

I just found something and don't know if this could be helpfull.

I used latest Dooble QT6 with latest QT6.2.x build
As often, the system get frozen (unresponsive) and had to power off/on to recover

Once again, the system got frozen but before power off/on, I tried to unplug/plugin my usb dongle used for the mouse and keyboard
and Oh !  it allowed me to use the keyboard and mouse for several seconds and frozen again and doding the same action allow me to have the hand on the system again....

What I could see:
- processor have a lot of high CPU spikes in continous (making it go into frozen state in loop interrupted by the usb mouse dongle which provides enough time to issue some commands)
- Trying to use the stop or reboot option from the xcenter will put it into a final frozen state.

During a between time of frozen state, I saw under theseus that dooble is always loaded into memory.
I could take a copy of theseus dooble process while having got mouse/keyboard back for a few seconds.

Remy:
Again, system frozen state.

Could get out doing: unplug/plugin USB wireless dongle then kill Dooble (do not exit but kill)

I've got a second time a frozen state and before killing it, I could take several theseus outputs I put into a zip file.
May it be helpfull to find the problem ?

Paul Smedley:
A process dump might be useful...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version