Skip to content
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

fix(launcher): 🐛 Fix installation popup #2356

Merged
merged 1 commit into from
Aug 26, 2024
Merged

fix(launcher): 🐛 Fix installation popup #2356

merged 1 commit into from
Aug 26, 2024

Conversation

zmerp
Copy link
Member

@zmerp zmerp commented Aug 26, 2024

No description provided.

@The-personified-devil
Copy link
Collaborator

How does this work?

@KyleCarr
Copy link

This change makes it so instead of creating a copy of the release channel version, it is actually mutable. This should save memory overall I believe right?

@zmerp
Copy link
Member Author

zmerp commented Aug 26, 2024

Basically i refactored away some logic for the popup, and in doing so we now need to call some code in a closure. Closures often means aliasing issues so I usually clone the variables needed. This time though we needed to mutate the variable (version) so the result was that the dropdowns didn't select anything anymore.

@The-personified-devil
Copy link
Collaborator

This change makes it so instead of creating a copy of the release channel version, it is actually mutable. This should save memory overall I believe right?

Yea that's what the diff says, but the question is why it's done. It's clearly a fix going by the diff message, so this somehow has to fix something

@zmerp
Copy link
Member Author

zmerp commented Aug 26, 2024

@KyleCarr this is not about memory saving. It was actually a bug caused by a refactoring. Most of the code in ALVR doesn't care about memory usage, apart some crucial paths while dealing with video buffers

@The-personified-devil
Copy link
Collaborator

This time though we needed to mutate the variable (version) so the result was that the dropdowns didn't select anything anymore.

Could've found that out myself tbh, I just keep getting blinded a bit by the lack of context from diff views

@zmerp
Copy link
Member Author

zmerp commented Aug 26, 2024

Yeah I would have never found this myself even staring at the code for hours. It was reported in the Discord server. It slipped my testing apparently.

@zmerp zmerp merged commit 404e7bb into master Aug 26, 2024
9 checks passed
@zmerp zmerp deleted the fix-launcher branch August 26, 2024 21:35
@The-personified-devil
Copy link
Collaborator

Yeah I would have never found this myself even staring at the code for hours. It was reported in the Discord server. It slipped my testing apparently.

Well yea, finding the initial bug, but finding the reason for the change is reasonably doable I think

@zmerp zmerp mentioned this pull request Sep 10, 2024
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