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.

Sign up for GitHub

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

Jump to bottom

Don't call UnregisterTypes() in ~JoltDestroyer #1025

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Don't call UnregisterTypes() in ~JoltDestroyer #1025

wants to merge 1 commit into from
+3 −2

Conversation

brakhane
Copy link
Collaborator

@brakhane brakhane force-pushed the double-linked-list branch 3 times, most recently from f52d0bf to 4cac1bb Compare January 16, 2025 21:41
@brakhane brakhane changed the title temporarily disable JoltDestroyer to work around Jolt bug Don't call UnregisterTypes() in ~JoltDestroyer Jan 16, 2025
@brakhane
Copy link
Collaborator Author

for now, removing UnregisterTypes() should suffice, but in the long run, it's probably a good idea to have a defined order of deinitialization, not just for Jolt, but for the all the other data where it matters as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

"Corrupted doubly-linked list"
1 participant
@brakhane