-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8262751: RenderPipelineState assertion error in J2DDemo #5227
Conversation
Provide correct pipeline state for MTLPaint after reset
👋 Welcome back avu! A progress list of the required criteria for merging this PR into |
Webrevs
|
@@ -948,6 +967,16 @@ - (void)setPipelineState:(id <MTLRenderCommandEncoder>)encoder | |||
renderOptions:renderOptions | |||
stencilNeeded:[mtlc.clip isShape]]; | |||
[encoder setRenderPipelineState:pipelineState]; | |||
} else { | |||
// Fallback to valid pipeline state |
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.
We should not call it a valid pipeline state. It is more of standard pipeline state with color 0 which we are using after reset.
We are hitting default MTLPaint without any texture(which seems to be the main root cause for this issue- state management problem) and we end up not setting any pipeline state. Please reword this comment.
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.
Also is it possible for us to just return at any earlier stage before we hit setRenderPipelineState() without valid texture or color?
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.
Yes, I agree it's not valid but standard or default state.
Also is it possible for us to just return at any earlier stage before we hit setRenderPipelineState() without valid texture or color?
The problem is that I'm unable to reproduce this failure. So, it's difficult to provide a robust empirical solution.
I have given all test run on metal pipeline. I will add my observation once it is done. |
Minor correction in the comments
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.
All test run is fine. Change looks good to me.
@avu This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 29 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 49b2789.
Your commit was automatically rebased without conflicts. |
Provide correct pipeline state for MTLPaint after reset
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5227/head:pull/5227
$ git checkout pull/5227
Update a local copy of the PR:
$ git checkout pull/5227
$ git pull https://git.openjdk.java.net/jdk pull/5227/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5227
View PR using the GUI difftool:
$ git pr show -t 5227
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5227.diff