Skip to content

Conversation

@chuckrector
Copy link

This updates the correct field rather than assigning the new max icon ID
to a local variable. Previously, if you had set an icon with ten images
and then later set a new icon with only one image, nine old images would
linger in the executable. If you revised your icon over time and reduced
the number of images each time, old icons from multiple different passes
would linger in the executable.

This bug was introduced by af37f5f which landed after the fix to a
similar bug that was described in issue #27.

This updates the correct field rather than assigning the new max icon ID
to a local variable. Previously, if you had set an icon with ten images
and then later set a new icon with only one image, nine old images would
linger in the executable. If you revised your icon over time and reduced
the number of images each time, old icons from multiple different passes
would linger in the executable.

This bug was introduced by af37f5f which landed after the fix to a
similar bug that was described in issue electron#27.
@tttony
Copy link

tttony commented Feb 7, 2022

I tested this and keeps the old icon data, I'm updating a .NET exe with 10 icons and tried to add a new one with 4 icons in it and the file size increased of the new icon

@dsanders11 dsanders11 self-requested a review February 7, 2024 18:10
@dsanders11 dsanders11 self-assigned this Feb 7, 2024
FirehawkV21 added a commit to FirehawkV21/rcedit that referenced this pull request Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants