-
Notifications
You must be signed in to change notification settings - Fork 48.8k
[Fizz] Clean up row that was blocked by an aborted boundary #33318
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
Conversation
Comparing: 50389e1...88098cc Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show
|
@@ -4636,7 +4629,6 @@ function abortTask(task: Task, request: Request, error: mixed): void { | |||
} | |||
} | |||
} else { | |||
boundary.pendingTasks--; |
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.
Since some of the paths below here are going to take the finishedTask
path and that does all the decrementing we need, we don't need to release anything above it. This is causing an extra task to be released (ending up in negative probably).
…#33318) Fixes a bug that we caused us to hang after an abort because we didn't manage the ref count correctly. DiffTrain build for [9c7b10e](facebook@9c7b10e)
Fixes a bug that we caused us to hang after an abort because we didn't manage the ref count correctly.