Fatal crash on Samsung Galaxy J5 (SM-J530F) #41
Comments
|
@gzm55 I remember you looked at some other Android-related issues, would you be able to check this one out? |
|
are other hash functions than xx() produce the same crash? does |
|
I have no physical access to this device now, since all our work is remote due to covid spread. All information i have is from QA team in my company, so i have limited options here. We are using xxHash to generate HMAC for requests. So value is mostly around 200-300 bytes long UTF-8 encoded string. It can never be null (it's kotlin, value is based on NonNullable string). If you need more data on that i will try to get this device somehow. |
|
how can relate this stack to hash function? |
|
That's the weird part. There is no my code on the stack. But if I remove call to hash function - everything else runs just fine. Add this to only one device it happens on - i think this might be some framework issue. And it's Samsung, which have a long history of breaking Android framework in many ways.. I know that this might be impossible to fix, but I hoped somebody might have some idea |
|
sorry, i have no idea~ |
|
@NekroMancer can u try to catch exceptions when call hash method: LongHashFunction h = null;
long v= 0;
try {
h = LongHashFunction.xx();
} catch (Throwable e) { throw new Exception(e); }
try {
v = h.hashBytes(value);
} catch (Throwable e) { throw new Exception(e); } |
|
I tried to capture exception, but it's fatal crash so nothing was caught. It just crashes the process entirely, bypassing even global exception handlers. I will try more as soon as I will get the device |
Hi,
I have it only on android device: Samsung Galaxy J5 (SM-J530F), but possibly there are other devices affected.
We have fatal crash that always happens when trying to hash byte array (contents does not seem to matter) using xxHash:
LongHashFunction .xx().hashBytes(value)Taken from LogCat:
The text was updated successfully, but these errors were encountered: