TÖRÖK Attila

> What size memcpy/memset are measured here? In the linked/attached profiles? I don't know, really. And since the `memset`s are mostly compiler-generated, I also don't know of any straightforward ways...

Just a heads-up: With https://github.com/ruffle-rs/ruffle/pull/5834 just merged, and Rust 1.58 (with its improved built-in memory loops) also being right around the corner, this got a lot less important for me...

> ... it's not uncommon for Android applications to have a SurfaceView inside a more complex layout - so SurfaceView doesn't take the whole space of Activity. That's definitely what...

On my local machine, `libc++_shared.so` is included in the APK when I point `$ANDROID_NDK_ROOT` to a 24.0.8215888 NDK, but not when to a 21.4.7075529 version, that's how I know this...

In fact, even if I manually copy `libc++_shared.so` into the APK, there are still unresolved references to symbols in it. Even if I `System.loadLibrary` it before the other shared library...

I was able to switch over to NDK r24 using https://github.com/nttld/setup-ndk, and now `libc++_shared.so` is correctly put in the APK on GitHub Actions as well. It was not immediately obvious...

> Note that you can link to lines in build steps directly: https://github.com/torokati44/ruffle-android/runs/5707487779?check_suite_focus=true#step:5:810 Right, thanks for the tip! I have set up a tiny repo with a bunch of crates...

Yes, without that, it doesn't work even with NDK 24. And I saw that Oboe has a feature to do this itself, which is neat - however, I am using...

This issue is still present in 6.0.

Thank you for the report and the fix! While your solution definitely works, it runs the check (of whether a result item belongs in the currently written run or not)...