Conversation
Regenerate the specs to implement the breaking change in Nitro related to the Kotlin HybridObject memory leak: mrousavy/nitro#1238
This is fully optional, but recommended for more flexibility for custom JNI registrations if needed.
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
1 participant
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.
Upgrades to Nitro 0.35.0, which contains a BREAKING CHANGE related to Kotlin HybridObjects (it fixes a critical memory leak, so it is advised everyone upgrades)
Steps I did (you can follow):
bigintwithInt64/UInt64(in this repo; none)bun nitrogencpp-adapter.cppcall frominitialize(vm)withregisterAllNatives()- this just allows you to register custom JNI natives in your libs, if needed.