Integer divide by zero in ConvertMipmap

I'm getting this crash trying to port to android, it still happens with a scene that is just a camera... I'm not sure what else could be causing it. What else should I be looking at?

ConvertMipmap(GraphicsFormat, void const*, GraphicsFormat, void*, int, int, int) 0x00000000d07a9811
(anonymous namespace)::UploadImages(ApiGLES*, unsigned int, unsigned int, int, GraphicsFormat, unsigned char const*, unsigned int, GraphicsFormat, int, int, int, int, TextureUsageMode, unsigned char*) 0x00000000d06c76ff
gles::UploadTexture(ApiGLES*, GLESTexture&, GraphicsFormat, void const*, unsigned int, int, int, int, int, unsigned int, TextureUsageMode) 0x00000000d06a9911
GfxDeviceGLES::UploadTexture2D(TextureID, TextureDimension, unsigned char const*, int, int, int, GraphicsFormat, int, TextureUploadFlags, TextureUsageMode) 0x00000000d06a947b
GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&) 0x00000000d06ee598
GfxDeviceWorker::RunExt(ThreadedStreamBuffer&) 0x00000000d06f8735
GfxDeviceWorker::Run() 0x00000000d06f86b0
GfxDeviceWorker::RunGfxDeviceWorker(void*) 0x00000000d06eba54
Thread::RunThreadWrapper(void*) 0x00000000d0cda938
__pthread_start(void*) 0x00000000ed3d4066
__start_thread 0x00000000ed36985c
__bionic_clone 0x00000000ed364c17

 

Hello, we're facing exactly same issue with our game. It affects few percents of our players so this issue is becoming quite urgent. We've deployed our game using Unity 2018.4.0f1. Is there something we can do about it?

 

I'm experiencing this on a Galaxy S7 with Unity 2018.4.4f1. Is there an active bug report for this problem? I couldn't find one.
Thanks!

 

Hello, bump.
Is there a solution to this problem in any Unity Version, preferably in Unity 2018?
I am still having this issue with Unity 2018.4.11 and can't figure out which texture is the problem and none of them even has mip maps turned on.
Thanks

 

We encountered this issue with Unity 2017.4.40. It seems that it's related to auto fallback of unsupported texture format. In our case, RGBAHalf format is not supported on some devices, then Unity tries to fallback it to RGBAFloat, and it's also not supported, then Unity fallbacks it to None(internal format). Because None format has some invalid configuration, when Unity tries to convert the unsupported format to this format, dividing by zero occurs.

In Unity 2019.4.0, this issue had been fixed(I'm not sure about the exact version): When a format fallbacks to None format, Unity ignores the format conversion.