Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[APP BUG]: QT from 0.5.0+ launching ANY game app always crashes with critical "pthread "error. QT 0.4.0 launching same games = no issues. #2099

Open
2 tasks done
asp28x opened this issue Jan 8, 2025 · 3 comments

Comments

@asp28x
Copy link

asp28x commented Jan 8, 2025

Checklist

  • I have searched for a similar issue in this repository and did not find one.
  • I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

When launching ANY game on QT 0.5.0+ application always crashes with the SAME critical "pthread.cpp"error and after while exits to OS. Note: Running version QT 0.4.0 with same games on the same desktop works without crashes.

Reproduction Steps

from 0.5.0 always the same output error:

[Debug] pthread.cpp:operator():292: Assertion Failed!
Failed to create thread with error -1073741790

shad_log.txt

pthread cpp_err

Expected Behavior

Please fix pthread CRITICAL error to run games without crashing and exiting to OS like in previous version QT 0.4.0

Specify OS Version

Win 11 24H2 26100.2605 1000.26100.36.0, X670E, R7 7800X3D, RTX 4070 Super, 32 GB 6400

@asp28x asp28x changed the title [APP BUG]: QT from 0.5.0+ when launching ANY game application always crashes with critical "pthread "error. QT 0.4.0 works OK. [APP BUG]: QT from 0.5.0+ launching ANY game app always crashes with critical "pthread "error. QT 0.4.0 launching same games = no issues. Jan 8, 2025
@Hermiten
Copy link
Collaborator

Hermiten commented Jan 8, 2025

Can this be cause by the kernel rewrite ?

@Trina232
Copy link

Trina232 commented Jan 9, 2025

Also having the same exact issue on any version besides 0.4.0 as well.

@StepanTaz
Copy link

StepanTaz commented Jan 11, 2025

Last working build for me is c019b54 and this error pops up in every build since 15ae7a0.

Likely culprit would be unity pt1 pr, i think?

Screenshot 2025-01-11 145632

Same hardware fwiw, 7800X3D and 4070 Super. Had this happen on both 23H2 and 24H2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants