Calling JS callback asynchronously from C++ thread. about react-native

[github-actions]

⚠️

Newer Version of React Native is Available!

ℹ️

You are on a supported minor version, but it looks like there's a newer patch available - 0.74.2. Please upgrade to the highest patch for your minor or latest and verify if the issue persists (alternatively, create a new project and repro the issue in it). If it does not repro, please let us know so we can close out this issue. This helps us ensure we are looking at issues that still exist in the most recent releases.

[cortinico]

Please create a repro using the Reproducer Template

[AbeereSpark]

@cortinico I have updated the issue with the required ReproducerApp.

[huzhanbo1996]

In jsi.h, it specifies that JSRuntime can not be accessed concurrently. This crash is expected.

Represents a JS runtime. Movable, but not copyable. Note that
this object may not be thread-aware, but cannot be used safely from
multiple threads at once. The application is responsible for
ensuring that it is used safely. This could mean using the
Runtime from a single thread, using a mutex, doing all work on a
serial queue, etc. This restriction applies to the methods of
this class, and any method in the API which take a Runtime& as an
argument. Destructors (all but ~Scope), operators, or other methods
which do not take Runtime& as an argument are safe to call from any
thread, but it is still forbidden to make write operations on a single
instance of any class from more than one thread. In addition, to
make shutdown safe, destruction of objects associated with the Runtime
must be destroyed before the Runtime is destroyed, or from the
destructor of a managed HostObject or HostFunction. Informally, this
means that the main source of unsafe behavior is to hold a jsi object
in a non-Runtime-managed object, and not clean it up before the Runtime
is shut down. If your lifecycle is such that avoiding this is hard,
you will probably need to do use your own locks.
class JSI_EXPORT Runtime {}