QT Creator's Data Integrity s**** a*** for years (time to fix it)

Vega4

Ok fellas,

We've been using QT for long years.

And we all know that the software needs to be installed within a VM because once in 1-500 debug sessions it is GUARANTEED to BREAK.

There's definitely something wrong with concurrency of file access or something along these lines.

One of us was running on a fresh new laptop with QT installed bare-bone. It took <30 builds for some data integrity issues to surface.

I QtCore  : Start
D         : [ZeroHung]zrhung_send_event: wp = 257, ret = 0
D         : [ZeroHung]zrhung_send_event: wp = 258, ret = 0
while parsing target library list: unclosed token
11:39:19:

None of us EVER had to reinstall Visual Studio and some of us have been using it for 20+ years.

QT Creator? We've been forced either to reinstall it or revert the VM back to previous state due to its data being corrupted dozens of times.

It shouldn't be like this.

Especially taking into account that QT Team keeps releasing s*** seemingly every couple of months when the basic code editing software is UTERLY broken.

We're not running magnetic drives with bad sectors but on laptops $2k+ each.

Running on windows, each and every QT version for past 4+ years. Building for iOS and Android.

kkoehne

@Vega4 said in QT Creator's Data Integrity s**** a*** for years (time to fix it):

And we all know that the software needs to be installed within a VM because once in 1-500 debug sessions it is GUARANTEED to BREAK.

Well, I don't know that :) But I'm probably not using Qt Creator in the way you do.

One of us was running on a fresh new laptop with QT installed bare-bone. It took <30 builds for some data integrity issues to surface.

I QtCore  : Start
D         : [ZeroHung]zrhung_send_event: wp = 257, ret = 0
D         : [ZeroHung]zrhung_send_event: wp = 258, ret = 0
while parsing target library list: unclosed token
11:39:19:

zrhung_send_event is related to Android debugging, it seems? Is that a crash when you're debugging an Android application? What is crashing, Qt Creator, the debugged app?....

Anyhow, I suggest you either reach out to Qt support (if you are commercial customer), or file a bug about this at bugreports.qt.io.

Vega4

It's around 10 people here all with same experience.

I highly doubt we're some some isolated cases.

Well I don't know how you use QT Creator we're talking about being able to DEBUG.. ANYTHING. To compile.

Maybe that's way too much. Dunno.

Take a look at the below. Suddenly we're not able to RUN.. but we're able to step over... no way to continue.
Feels like an early alpha BUT it's most recent stable 6.0.2

Vega4

yeah we'll be opening bug reports.. but seeing how these are fixed in months (if ever) and seeing the scope of these things

just try to download latest version of QT creator on Windows and use the auto-setup Android SDK functionality. it's now broken as well. Hint: you better click that you DO NOT accept licenses as it would attempt to wait for these indefinitely to be never delivered from server. Also, even when one follows the manual way.. it would still complain about missing stuff re-download duplicates and attempt o go ahead.

Once you got over it manually you just try to debug ANY app with automatic settings You'll get to see what I mean.

We've done so on two laptops yesterday. None of the auto-configuration settings worked in our case. Had to change CPU type in settings, had to enable wait for debugger specifically in the mobile phone's settings, had to select the specific app to be debugged. And after all that once breakpoints are set in QML these are hit.. you may step over but the run/continue button is GONE.

One may not freeze the entire execution process by simply hitting pause. F5 has no effect. Just take a look at the screenshot above, can you see a continue button? the breakpoint just got hit right? ;] one may press f5 1000 times it wouldn't continue. No we haven't Photoshop'ed this.

No idea how you use QT Creator. Glad it works for you! We've also worked with it for years for better or WORSE.

or you just try to attach to an already running process on Android.

Seems like basic stuff, huh? (we've NEVER seemed to be able to do so).

It's not some noobs sitting here trying to play around with programming. I can assure you of that.

And yeah it seems to have some serious concurrency issues with file access (probably) as from time to time it lands with corrupted data in some places rendering it unable to proceed with debugging deployment. Which is when we revert the VM.

Doom upon those who run QT Creator bare-bone.

Some of us manage to have it running for months but s*** happens anyway sooner or later.

Vega4

@kkoehne said in QT Creator's Data Integrity s**** a*** for years (time to fix it):

I QtCore : Start
D : [ZeroHung]zrhung_send_event: wp = 257, ret = 0
D : [ZeroHung]zrhung_send_event: wp = 258, ret = 0
while parsing target library list: unclosed token
11:39:19:

This very thing happened to us twice... within 48hours ;] ;] luckily we all are now on VMs and simply reverted them back to a 'safe snapshot'. go figure. the overall experience in terms of widely understood 'stability' is way worse than with the previous branch and I thought the previous needed lots of improvements.

Maybe it's a QT <-> Android SDK specific issue.

And let us be clear - it just happens. There's no hint indicating in which file the 'unclosed token' is. We submit code to SVN => revert to previous snapshot => update code from SVN and work further. which makes it a 100% QR Creator-specific issue.

Vega4

here you go, the story continues.... every now and then... QT Creator goes like this for no imminent reason

and one has to wiat until it does all the repackaging.. even for a package whose content has NOT changed.. wait for minutes just to see the above...

In QT creator 6 the QT Quick designer for some reason is DISBALED (yeah thanks for notifying the user in ANY way).

And nope it's not a bad cable. Connection to adb is never lost.

JKSH

@Vega4 said in QT Creator's Data Integrity s**** a*** for years (time to fix it):

In QT creator 6 the QT Quick designer for some reason is DISBALED (yeah thanks for notifying the user in ANY way).

https://www.qt.io/blog/qt-creator-6-released Under "Editing"

Vega4

@Vega4 Fellas, not to say that everything is QT Creator's fault... here it was OURS... there was not enough memory on the particular device for successful deployment.

Vega4

@JKSH Kindly thank you, found that out already, can't edit most of our QMLs though due to this bug

Vega4

Clean doesn't help... reverting VM back again...

mchinand

What VM software do you use? Have you tried developing with a Linux guest OS?

Vega4

@mchinand We've been using Windows 10 as a guest OS, using VMWare virtualization.