Having issues starting a majority of QT-created apps
-
@darkaegis maybe this is a good opportunity for you to switch to and learn Ubuntu (there are plenty of Steam games that work) :-))
-
Haha, I'm somewhat familiar with Ubuntu - I used it years ago in college and I dabble occasionally, but I've got far too many Windows-exclusive Steam games as well as Lightroom and Photoshop (for my job) that demand a Windows PC.
Plus, many of the issues I've got right now revolve around Vive, which I hear has pretty close to zero Linux support.
If anything, I'll probably dual-boot at some point in the near future, but I don't think I'll do it as a solution to my issue. :D
Something just came to me, by the way - Origin recently overhauled their platform - presumably into qt5. That may have been why I didn't have the issue before but am having the issue now. I can't find a way to install the old version of Origin since they use a web installer and it downloads the newest version by default, but I can say that the graphical glitches and crashes I get in the newest installer aren't present in their older versions.
Obviously I can't say it conclusively, but I can say that the problem seems to be restricted to applications made with Qt, regardless of how resource-heavy they are. Although I'm not sure why some Qt apps work with glitches and some crash outright.
-
BTW, perhaps it's some specific Qt behavior that triggers the glitches. Now I'm thinking about the NX settings, have you tried disabling NX in BIOS?
Edit: you can try it from inside Windows 10, open an elevated CMD window:
bcdedit.exe /set {current} nx AlwaysOff -
Yeah, VLC is actually my primary video player, and seems to be one of the Qt apps that doesn't trigger the behavior. I also use KeePass without error very regularly. I wonder if it has something to do with a specific version of Qt.
I disabled XD in bios - no luck. Same results.
And seriously, thanks again for all of the help. Even if we can't nail this down I appreciate it.
-
Let me know logs or anything might help. I'm willing to do whatever, at this point, to nail this down. A bit of extra info:
The version of qt in the crashing Origin is 5.6.0.0.and it points to Qt5core.dll and I can (usually) get moments past logging in before crashing outright.
The version of qt in the crashing EasyAntiCheat is 5.3.1.0 (although, technically, this one may not be related because I'm just getting a failure to start and no actual error in the event log, but it is inexplicably failing to start, so I can only assume that this is part of the issue)
The version of qt in the crashing Stellarium is 5.6.1.0 and it points to qt5core.dll
The version of qt in HTC Vive setup software is 5.5.1.0 and I don't even get a splash screen before starting. It also points to qt5core.dll.
SteamVR uses 5.5.0.0 - and while it does work without crashing outright, there are weird text glitches in the menu, similar to what I see in Origin before it crashes. I'm unable to get to it at the moment, but this guy was having a similar issue and you can see what it looks like here.
.It'll often (but not always) look like that in every menu in the app, including settings. In addition, sometimes the background of the settings menu will fail to load and the whole window will be transparent.
Videolan works fine and seems to be using an older version of Qt - Qt4, unless their documentation is outdated. Even so, their latest stable version is still old enough to come before this bug I'm having.
Would this be a proper bug to submit officially to the bug tracker? Considering I'm not encountering it (seemingly) with any non-Qt apps on a very heavily used computer, I can only assume something is happening between the newest versions of Qt and my specific hardware/software setup.
-
Hi to submit it as a bug, best would be to have a small working, reproducible example.
For example. if you could try download and install Qt on your Windows 10 and build a simple Widgets app (no coding necessary, just select a Widgets app and Build/Run.Then when you try to start that simple Widgets app and it glitches out, we're in business.
-
Unfortunately, since I think the Qt installer is based on Qt, it never makes it through completely. Sometimes it chokes when it's downloading the packages, sometimes it chokes on the "selection" screen, and sometimes it chokes halfway through installation, but it never makes it through completely without crashing or messing up to the point where I can't go any further. Similar story with the offline installation.
I'll keep trying to install it, but I don't think I'll have any luck.
-
@darkaegis Oh for sure the installer app is 100% Qt.
But if you another Windows PC around, you could install Qt and build a vanilla Widgets app on that PC, then run windeployqt on the .exe and copy the files over to your main culprit. -
It does look like all of them are using their own copy of the Qt dlls. At least, for every app that I'm having errors, the Qt dlls are either within the application folder, or within a temporary folder created by the application (in the case of the Vive installer).
I also realized something - a lot of the same errors I had on the Linux install, I had with the Windows install before it crashed or just didn't work outright. There's a possibility that my issues do extend to Linux, although it seems as if they were less severe since I was able to get the program running, at least.
Installing it on my media PC right now to test. No errors at all, predictably.
-
Well, this is frustrating. I've built and successfully run chip, colliding mice, and Google Suggest with no errors or issues. Seems I need either something specific, something more complex, or both to trigger it.
Problem is, since I have no idea how this all works, when I try to build more complex programs, they're starting blank because I have no idea how to compile and run them with their resources for use outside of Qt. As of now, though, I'm at a dead end. I'll attempt to build and run a few more of these over the weekend.
-
Well, from a Qt standpoint this is somewhat good news, I mean that simple apps perform nominally.
Probably means that those more complex, real Qt apps use some additional resources that makes them go south. Have you tried some sound demo?
BTW: have you got some fancy hardware plugged in to your USB connectors? Like video-camera? Pull 'em all out :-)
Edit: also try removing your network cable. I know, I'm somewhat at my wit's end.
Edit 2nd time: if you want to go full medieval on this one, you could try installing an older version of Qt on your media PC (say that 5.6.0 version that Origin is built with) and test some demos on that version on your Win10.
-
That's good to hear. I've run a few more QT apps in the meantime. Subsurface, which uses 5.5.1.0, Teamspeak, and Telegram seem to work fine, so no idea what might be triggering it at this point.
I'll try a sound demo when I can get around to it. Wife is home, so the media center PC is occupied at the moment. In the meantime, I'll try unplugging everything from my USB drives. I don't have anything too fancy, really. Gaming keyboard and mouse, XQD reader, and Steam Remote dongle. I'll see how the games fare with everything unplugged.
I tried disabling my NIC completely earlier, because Origin was hinting at some sort of network issue (igoproxy64 was faulting half the time), but I'll try unplugging ethernet as well.
-
I had a potential breakthrough. Well, at least it may help scratch a few things off of the "potential issue" list and push the "more complex apps" theory, unless it's somehow unrelated.
I was kind of going down the list of Qt apps and seeing what crashed and what didn't, when I came to Marble.
It didn't crash upon launch and was stable until I spun the "globe" around a few times, when it stuttered, then crashed on me. I was monitoring my CPU and GPU use in external programs - very little to no GPU was used for the app, but the CPU was hovering between 9 and 20 percent.
Oddly, the first time it crashed pretty quickly, but the second and third times took a bit longer. I cleared the cache and it crashed again almost immediately, even though it doesn't seem to be using much more CPU. Every time I clear the cache it either immediately crashes or crashes in a few seconds.
Not 100% sure what that would point to, but it's something, at least.
