-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Migrations don't appear to dispose resources correctly #4605
Comments
Ideally a C++ repro that uses the Object Store APIs is what we'll need to debug this, but at the very least I'll need to see the code of your test, as well as any error information (exception message, stack trace, debugger screenshot, etc.). |
I'll prepare a simple test case that reproduces this. |
@fealebenpae I've created a simple repro in this PR: realm/realm-dotnet#2334. I'm guessing you can run the .NET tests, but let me know if you want to look at it together. |
➤ Jørgen Edelbo commented: [~yavor.georgiev] since there is a repro test case this should be ready for work. Assigning to you, as you are the only .NET guy around. |
@fealebenpae @nirinchev is this still relevant? |
➤ bmunkholm commented: [~nikola.irinchev@mongodb.com] [~yavor.georgiev@mongodb.com] Still relevant? Will you handle or should someone in the Core team? |
➤ nirinchev commented: Let's close this - there's nothing to be done on the Core side. |
I have a migration test that fails during cleanup on Windows because NTFS doesn't allow deleting a file that is still in use. It could very well be something that I'm doing wrong, but as far as I can tell, when a migration callback is invoked something starts using the Realm file and never releases it. For reference, here's the .NET-specific code that deals with migrations and I don't see obvious issues with it.
The text was updated successfully, but these errors were encountered: