On Thu, 15 Apr 2021 16:43:08 GMT, Matthias Bläsing
wrote:
>> The functions from FileSystemJava are called from different threads the
>> root problem manifests because the JNI FindClass function behaves
>> differently when called from a context that is the ancestor of a java
>> frame compared to
On Mon, 19 Apr 2021 14:25:36 GMT, Arun Joseph wrote:
>> Matthias Bläsing has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Review fix: Use correct bug id
>
> The test and changes looks good.
@arun-Joseph @kevinrushforth thank you both
On Thu, 15 Apr 2021 16:43:08 GMT, Matthias Bläsing
wrote:
>> The functions from FileSystemJava are called from different threads the
>> root problem manifests because the JNI FindClass function behaves
>> differently when called from a context that is the ancestor of a java
>> frame compared to
On Thu, 15 Apr 2021 16:43:08 GMT, Matthias Bläsing
wrote:
>> The functions from FileSystemJava are called from different threads the
>> root problem manifests because the JNI FindClass function behaves
>> differently when called from a context that is the ancestor of a java
>> frame compared to
> The functions from FileSystemJava are called from different threads the
> root problem manifests because the JNI FindClass function behaves
> differently when called from a context that is the ancestor of a java
> frame compared to when called in isolation.
>
> A segmentation fault is observed