Skip to content

Conversation

@jamescrosswell
Copy link
Collaborator

Fixes #3653

Ideally we'd be able to reproduce this in a unit test to prevent a regression.

Regardless, it looks like there might be a timing issue where sometimes the writer tries to do something with the file after File.Dispose() has been called. I've moved the writer inside the try block to ensure writer.Dispose() is called before file.Dispose(), which should avoid the problem.

Copy link
Contributor

@bricefriha bricefriha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me.

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.

Failed to persist session on the file system.

3 participants