Without being able to test with your png it will be impossible to test

It is very likely the PNG resolution is high, or server memory limit is low, or both.
In general, PHP GD need a lot of memory for large images.

Without detailed information it is hard to tell what is going on. There can be 1000 reasons.
Addittionaly to "Uncaught (in promise) Error" the browser may show actual error, sometimes.

it should only not show the image that it has issues with, but should show all other images.

I do not think it is realy possible in Media manager.

this was the png in question.

Can't confirm:

Unfortunately github probably changes the image when you upload it so we cant test with it. Perhaps you can zip the image and then share the zip - that might work

ov002_02.png.zip
This is the zipped png file

Thanks for doing that. Unfortunately I am unable to replicate your error. The only thing I can think of to check at this time is to see if you have the php extensions gd and fileinfo

You can determine this by checking the system information available fropm the system dashboard

@cloudfaction also using the new uploaded file i'm unable to reproduce the error you have reported:

ov002_03.png.zip

my bad, it was this file.

Thanks for doing that. Unfortunately I am unable to replicate your error. The only thing I can think of to check at this time is to see if you have the php extensions gd and fileinfo

You can determine this by checking the system information available fropm the system dashboard

both are the same as your screenshot.

Still no problem with 003

If you open and save the file with another graphic program do you still have the problem?

no, it shows, but you can see that the bottom of the image is gone. the png is not faulty. but still it should not block my entire media manager, in my opinion.

I have opened the png in multiple programs and in 003 there is empty space in the bottom 2/3

yep it is. but that is not the point. i have a joomla install with the mediamanager stalling on this image. but if no one can reproduce this, i guess closing the issue is the best. thank you all for your efforts!

Can someone close this as has been requested - thanks