-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Calling function flushAndWait will always block on it if I not run it on main thread. Under the mac arm64 architecture. #8137
Comments
Does this happen with the Metal backend too? |
pixelflinger
added
bug
Something isn't working
macos
Issue/feature request for macOS only
ios
Issue/request for iOS only
labels
Sep 26, 2024
Yes, I use the filament example
the error msg :
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I want to use off-screen rendering to do something. When developing on the Mac platform, for some reason, I must work on non-main thread . Then I found that if I render on a non-main thread, it will be blocked in flushAndWait,This happened to me on
Mac(M1)
, but not on Windows.To Reproduce
Steps to reproduce the behavior:
the code like this:
Expected behavior
hope can on non-main thread render image (on mac M1 arm64)
Screenshots
no
Logs
no
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: