[Since 0.6.13] Crashes on thumbnails load while running on ARChon(1.2/2.1 Chrome 64-bit, Windows 7 x64) about ehviewer HOT 17 CLOSED

Crash every time ?

from ehviewer.

Double-checked, yes it crashes every time (it loads title and other things fine but crashes right before any thumbnail shows up)

from ehviewer.

I checked the code. It should not happen. But I do some warning thing about generic type in the code of cache. Maybe the code is error for the platform.

from ehviewer.

0.6.11.2 work fine and 0.6.12 does not ? I only add web login in 0.6.12. Could you please show the error log in 0.6.12 ?

from ehviewer.

Sorry, my bad... I don't know how it happened but the apk I had with the name of 0.6.12 acturally was 0.6.13, so there was nothing unaccountable.

from ehviewer.

It's OK. I will fix the warning.

from ehviewer.

I'm having the same issue here - program crashing on physical device with android 4.4 since 0.6.13, logs are exactly the same as above.

from ehviewer.

@Laforeta Could you please tell me your phone model ?

from ehviewer.

@seven332 Motorola Droid Maxx (XT-1080M). I can install and run all pre-0.6.13 versions without crash so this seems to be a specific issue.

from ehviewer.

@Laforeta Did you phone use ART as runtime environmen ?

from ehviewer.

@seven332 No, it was on Dalvik the whole time. I tried switching to ART and it did not help.

from ehviewer.

@RadarNyan @Laforeta I hope it work now.
Please download the apk here https://mega.co.nz/#!BtEXWBAS!HxibUXmfTZSkWq3h8dewEtabGq7m3VLTbJ8zWOy9zWM

from ehviewer.

@seven332 Thank you very much for your time. I tried the linked build and it still crashes the same way as before. If this only affects a few devices then perhaps you should not worry about it - I will try to do some debugging on my end. Thanks again for your help.

from ehviewer.

Recent Chrome Update breaks ARChon (I can't even run the 2048 sample app) and the app worked fine on my phone, so there's nothing I can do... will check once ARChon back to work though.

from ehviewer.

It is my mistake, I didn't check the log carefully. I should have gotten the reason earlier.
Actually it is a bug of kitkat. I checked the source code of Android.
In kitkat-release branch, it will throw NullPointerException if mBuffer is null

1169    public final int getAllocationByteCount() {
1170        return mBuffer.length;
1171    }

In kitkat-mr1-release branch, they fixed the bug

1169    public final int getAllocationByteCount() {
1170        if (mBuffer == null) {
1171            // native backed bitmaps don't support reconfiguration,
1172            // so alloc size is always content size
1173            return getByteCount();
1174        }
1175        return mBuffer.length;
1176    }

So just avoid invoking this method.

It should work this time.
https://mega.co.nz/#!kpFVhZJI!mn6e2sK2IMl1sSKqh8KpT_3XVoVmhyKoevnAiOsHsns

from ehviewer.

@Laforeta Please check the apk above.

from ehviewer.

@seven332 that did the magic - it is fully stable now. Thanks heaps! This explains why people on 4.4.1 and later versions of Android never had the issue to begin with.

from ehviewer.