fix: ensure ASAR integrity buffer on windows is valid#1878
Merged
MarshallOfSound merged 1 commit intoelectron:mainfrom Feb 9, 2026
Merged
fix: ensure ASAR integrity buffer on windows is valid#1878MarshallOfSound merged 1 commit intoelectron:mainfrom
MarshallOfSound merged 1 commit intoelectron:mainfrom
Conversation
|
Thanks for opening a pull request! Here are some highlighted action items that will help get it across the finish line, from the
Development and triage is community-driven, so please be patient and we will get back to you as soon as we can. |
Member
|
I think the semantics here should be: small buffers are allocated form a pool and when you need the actual ArrayBuffer you need to get a slice of the underlying arraybuffer like so. |
92f7237 to
60e459d
Compare
Contributor
Author
|
@MarshallOfSound should be good now :) |
MarshallOfSound
approved these changes
Feb 9, 2026
|
Thanks for your contribution! 🎉 |
|
🎉 This PR is included in version 19.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summarize your changes:
This pull request fixes #1873 which was caused by the change in 8d64aa1 to
resedit.jswhere.bufferwas added when setting the data for the integrity resource resulting in it being written corruptly to the finalexe.The documentation for Buffer.buffer warns the result "is not guaranteed to correspond exactly to the original Buffer". This not corresponding exactly to the original buffer seems to be what is resulting in the corrupt integrity data as reverting that change results in the correct data being written to the resource and Electron starting as expected with integrity checking enabled.
It does make me wonder if the other uses of
.buffercould be causing issues but I did not revert the other.bufferas it seems to be just matching up with behavior above it.