fix: re-entrancy issues in webContents.loadURL()
#48004
Open
+54
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Closes #40809
This fixes a crash possible when calling
webContents.loadURL()
from a failed call's catch handler. Essentially, a re-entrant navigation triggered from thedid-start-navigation
event causes the in-flightNavigationRequest
to be destroyed before Chromium marks it safe, tripping theis_safe_to_delete_
DCHECK here.Fix this by monitoring potential re-entrancy sites and failing if we try to call
loadURL
again at a dangerous time.Checklist
npm test
passesRelease Notes
Notes: Fixed a crash possible when calling
webContents.loadURL()
from a failedwebContents.loadURL()
call's catch handler.