Repository navigation
Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
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.

Problem
After the v1.35.0 release, several users reported an exception at launch:
Cause
@Halbann reports:
Apparently Steam sometimes corrupts one of the important files in its database and then just leaves it there (in addition to leaving a bunch of empty folders after it disables a DLC, see #4002). (Windows may be partly responsible, since this all-null file strongly is strongly reminiscent of #4078, which our code would never cause if the OS ran it as written.) Once this happens,
KeyValueValue.KVSerializer.Deserializethrows an exception when asked to read such a file.Changes
Now if
Deserializethrows an exception, we log a warning and continue with the other.acffiles.We will continue to investigate this as other affected users report back, in case they are experiencing the same issue with different causes, but for now this is one definite problem we can address.
Fixes #4197.