Android crash

Hi,

I’ve hit wierd bug. If I have datatable in project that have enum field and string array field. And enum names have underscore symbol in it “_”, time to time packaged build on Android crashes.
In some cases app launches just fine, in some cases crash during startup and in some cases assesind data from such datatable causing crash.

Here is project were I was able to reproduce it:
https://drive.google.com/file/d/1neoe9JoKXtUGJHixGpf7V0zM3XhwzRYH/view?usp=sharing

Log all time a bit different, leading to null pointer dereference at some poit.

06-29 12:46:24.070 17002 17002 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-29 12:46:24.070 17002 17002 F DEBUG   : Build fingerprint: 'Sony/H4413_RU/H4413:9/50.2.A.3.55/357197128:user/release-keys'
06-29 12:46:24.070 17002 17002 F DEBUG   : Revision: '0'
06-29 12:46:24.070 17002 17002 F DEBUG   : ABI: 'arm'
06-29 12:46:24.070 17002 17002 F DEBUG   : pid: 16887, tid: 16923, name: Thread-2  >>> com.YourCompany.AndroidCrash_425 <<<
06-29 12:46:24.070 17002 17002 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-29 12:46:24.070 17002 17002 F DEBUG   : Cause: null pointer dereference
06-29 12:46:24.070 17002 17002 F DEBUG   :     r0  c136dee0  r1  00000000  r2  0000001e  r3  03ba28c6
06-29 12:46:24.070 17002 17002 F DEBUG   :     r4  00000001  r5  0000000f  r6  00000000  r7  00000000
06-29 12:46:24.070 17002 17002 F DEBUG   :     r8  c234f8e0  r9  00000000  r10 c2348cb0  r11 d1990ce0
06-29 12:46:24.070 17002 17002 F DEBUG   :     ip  e0000000  sp  d1990cb8  lr  ca6d9610  pc  ef4421a0
06-29 12:46:24.316 17002 17002 F DEBUG   :

Can you find out which datatable entries are crashing it when you access them?

Yes. It’s just like I said, very simple datatable with two fields: enum and string array. It’s all blueprint based. And I even don’t need to access it. Crash occurring time to time at android build launch. Crash conditions: enum names should have underscore symbol in it ("_") and string field should be array.

If I remove these conditions, all launching just fine. I spend tree days in tests so I’m on 90% positive about it :slight_smile: Win build works fine btw.

AsyncDataLoading class appears in logs and I’m assuming that maybe there is some serialization/de -serialization issue? But why only on Android? :expressionless:

Hmm that sounds like a defect, something to submit as a Bug report to Epic.