Fix AccessViolationException on application shutdown (Ctrl+C) #48
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.
🚀 Fix for Issue #6
This PR fixes the
AccessViolationExceptionthat occurs when shutting down the application with Ctrl+C.🔍 Problem Analysis
The issue was caused by improper disposal of the
SplitMemoryLinks<ulong>instance during application shutdown. When the user pressed Ctrl+C, the application would terminate abruptly without properly disposing of memory-mapped resources, leading to:✅ Solution
Implemented comprehensive resource cleanup through:
Data.csto track the disposableSplitMemoryLinksinstanceDisposeLinks()method with exception handling to prevent disposal errors from causing crashesLinksLifetimeServicehosted service to handle application stopping events📂 Files Modified
🧪 Testing
🔧 Technical Details
The solution uses ASP.NET Core's
IHostApplicationLifetimeto properly handle shutdown signals (SIGTERM/SIGINT) and ensures that:This approach is robust and follows .NET best practices for resource management in web applications.
🤖 Generated with Claude Code
Resolves #6