Up to 60x worse performance on Chrome for Android

[StudioPetrikas]

Hi,
First of all, thank you very much for your work on this module. I've been working on a photography-related webapp, and it's been very useful at reading/writing metadata.

However, some of the testers have reported really bad performance on Chrome for Android, and, possibly, later versions of iOS.

Here's an example file:
https://github.com/StudioPetrikas/DNG_Test_Imagery/blob/main/Mo_Edge20_ColourfulStreet.dng

While it takes up to a second on Desktop and Firefoxf for Android, on Chrome for Android it can take up to a minute to load.

It seems that resolution / size makes no difference, as I've also tested files that are sub-1000px in size.

I know that this is a niche problem, but all I can do is try opening a ticket and hope that it's not a big problem to fix.

Thanks again!

[andrewmd5]

To clarify on Chrome for Android it takes a minute for it to load for reading or writing? I don’t have an Android device handy so investigating will take some time.

[StudioPetrikas]

Sorry, yes, reading.

I thought maybe it was my bad implementation somehow, but it's also reproducible on metadata.jp

[andrewmd5]

Gotcha. I tested in iOS and it worked within a second there; I’ll go pickup an Android device over the weekend and see if it’s a bug that needs to be reported downstream to Chrome or if I can find a workaround.

In the meantime you can try building zeroperl yourself and decreasing the stack size to see if that helps. I suspect that could be it.

[StudioPetrikas]

Thanks.

I've been using iOS 18.x without a problem, but the testers reported that it's slow-ish on iOS 26. I've just updated and can confirm that it's much slower on iOS26.2 (~15-20s to read)