dpisklov
commented
4 years ago @gzm55 I remember you looked at some other Android-related issues, would you be able to check this one out? Thanks
Closed jakoss closed 3 months ago
dpisklov
commented
4 years ago @gzm55 I remember you looked at some other Android-related issues, would you be able to check this one out? Thanks
gzm55
commented
4 years ago are other hash functions than xx() produce the same crash? does value equal to null? what is the length of value? hashBytes(new byte[0-16]) always produce the same crash?
jakoss
commented
4 years ago 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.
gzm55
commented
4 years ago how can relate this stack to hash function?
jakoss
commented
4 years ago 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
gzm55
commented
4 years ago sorry, i have no idea~ need more info, so better to get the device for debugging and test some other hash methods.
gzm55
commented
4 years ago @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
tgd
commented
3 months ago Closing this out as no work is planned on this at the moment. Please comment on this issue if you would like it re-opened. If you would like to expedite the development of this please get in touch with us here for commercial support: https://chronicle.software/contact-us/
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:
Taken from LogCat: