`v8::String::new_from_onebyte_const` crash on Android aarch64 about rusty_v8 HOT 5 OPEN

It might be related to the vtable layout for one-byte consts.

from rusty_v8.

I shall say: Ouch. Mea culpa.

from rusty_v8.

I think we may just need to special case vtable layout for Android as well -- the question would be what that layout is. Perhaps the relative vtable ABI?

from rusty_v8.

Yeah; it might be as easy as applying the Windows vtable layout (only one destructor) for Android but of course the issue is testing the change.

I'm thinking of a way to, at test time, verify the vtable layout so as to ensure any issues on different platforms become build time issues instead of runtime ones.

from rusty_v8.

There is test, but just skip for Android:

  // one-byte "const" test
  #[cfg(not(target_os = "android"))]

from rusty_v8.