fix bug: move jerry_make_api_unavailable into the end of jerry_cleanup #1277
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.
In the old jerry_cleanup, it first jerry_make_api_unavailable , then call
ecma_finalize
->ecma_gc_run
During gc, it may call
which will jerry_make_api_available (); in the end
So in this way, we can't call jerry_init after jerry_cleanup, because
In the patch, we move
jerry_make_api_unavailable()
to the end ofjerry_cleanup
to make sure the jerry_api_available==false after cleanup