-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
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
Fix Command Queue Crash #50193
Fix Command Queue Crash #50193
Conversation
Here are two related issues reported which show CommandQueueMT in the stacktrace, both filed within the past two weeks (post rewrite): AndreaCatania reported a similar issue in rocketchat, but I think a GitHub issue was never filed. Here are the stacktraces from June 23, and later on June 27th respectively: Interestingly, there was one issue filed on May 29th, before CommandQueue was rewritten, which indicates 8b19ffd as the commit which caused the issue: |
@akien-mga that is odd, judging from the stack trace it should, I will give it a check later today. |
@akien-mga Not sure what you tested, but: #49895 does not crash for me, the new code catches the error properly: |
59f4a2d
to
2d59b99
Compare
Ok, I think it should be perfect now, went all cases of material_set_param and id not find anything else that could cause trouble. |
Edit: Ignore this, I was testing an older version.
#49895 still crashes for me with the current commit of this PR:
System specs:
|
* No longer allow sending an object (texture) to the server as material parameter * Keep a parameter cache locally in ShaderMaterial
2d59b99
to
d41e3f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was testing the wrong commit previously. After testing the right commit, I can confirm it works fine and fixes #49895.
Thanks! |
Fixes #49895
Fixes #49201