Krzysztof Magiera

I'm not entirely sure what the issue is. It seems like something that you can reproduce easily, in which case it'd be great if you could send a small app...

Hi all! Thanks for reporting and all your comments. I wanted to point out that "EXC_BAD_ACCESS" is a typical error message related to accessing corrupted/cleaned-up/out-of-scope memory and even thought a...

This looks more like how I'd imagine. Thanks for sending @farfromrefug. Willing to send a PR with this change maybe?

Thank you for working on this however I need to point out that this PR is very difficult to review at the current state. What could help is to split...

Thanks @robertwt7 for reporting however the description lacks a lot of details and does not make the issue actionable to us. The code you provided has missing components, so please...

At first glance it looks like "automatic integrity protection" messes something up with refleciton. React Native on Android uses reflection to map native methods such that they can be called...

As @andrews said: JIT is enabled, we don't use DFG and FTL. Closing this as I ensured that it is a while ago. BTW: ~.5MB is uncompressed for single CPU...

That link to trac is 14months old. We managed to compile JSC with FTL JIT, would be good to actually verify it runs

Thanks @ben-manes for your report. We discussed this issue internally on contributors discord and with help from some jsc maintainers figured one other approach to fix this. We are hoping...

Thanks for this comprehensive report @rotemmiz We've spent some time debugging arm64 crashes last year and I'm glad to see that this one is easily reproducible. Please feel free to...