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

[qt 6.8.0] Runtime crash because of ICU #42661

Closed
troopa81 opened this issue Dec 12, 2024 · 3 comments
Closed

[qt 6.8.0] Runtime crash because of ICU #42661

troopa81 opened this issue Dec 12, 2024 · 3 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@troopa81
Copy link

Describe the bug

When building QGIS, I got a crash when starting the application inside the icu dll.

If we build without ICU, we get no crash and the application runs fine.

An issue with ICU has been fixed in 6.8.1 but I understand it has been patched so we are supposed to be OK on this.

Actually Qt is not building and releasing their binaries with ICU, so should vcpkg do the same until they maybe change their mind ?

Environment

  • OS: Windows
  • Compiler: Microsoft Visual Studio 2022

To Reproduce
Steps to reproduce the behavior:

  1. Build QGIS (sorry, I don't have a simple example program to test with)
  2. Run it
  3. See crash

Expected behavior
No crash

Failure logs

Crash screenshots in Visual Studio

Stacktrace bottom
Image

Stacktrace top
Image

Additional context

None

@JonLiu1993 JonLiu1993 added the category:port-bug The issue is with a library, which is something the port should already support label Dec 12, 2024
@JonLiu1993
Copy link
Member

@troopa81, Thanks for your issue. I suggest that we wait for the upstream to solve this problem and release a new version of Qt. We can directly upgrade the version instead of patching. What do you think?

@troopa81
Copy link
Author

Looking at more closely, it seems that the vcpkg included patch doesn't include this fix, avoiding infinite recursion, which looks like exactly as the issue I get.

So, 2 possible solution:

  • patch 6.8.0
  • wait for 6.8.1

I'll try to propose the patch for 6.8.0 if I manage to find the time

@troopa81
Copy link
Author

6.8.1 is already approved, so I'll test with 6.8.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

2 participants