Other World Mapper Forum

Things are getting interesting! Instead of Too many profiles, this one's showing up now too!

I've been trying to track down the cause of these error messages. Individual JPGs seem to cause them. I'm attaching one that does it every time here with OWM, even though other programs have no problem with it. The problem occurs when one in OWM opens the folder (directory) that contains the PNG. Other programs have no problems with this PNG.

Servus,

Thank you so much for the report and sorry for the slow replies (yes, regression testing ).

Those errors are from improperly formatted png headers. libpng is extremely picky about it, and we use it Linux and Mac, and partially in Windows.

It shouldn't cause a crash, but it's possible it's confusing libpng (we'll investigate with the file you provided). We are stripping those errors from our custom build of libpng, so they shouldn't be there going forward. Hopefully we can solve the crash too.

FYI, anyone using those assets in a program that uses the OS's libpng in Linux (and not a custom build) will get those errors.

Thank you!

- Alejandro

Kanchou wrote:Those errors are from improperly formatted png headers. libpng is extremely picky about it, and we use it Linux and Mac, and partially in Windows.

It shouldn't cause a crash, but it's possible it's confusing libpng (we'll investigate with the file you provided). We are stripping those errors from our custom build of libpng, so they shouldn't be there going forward. Hopefully we can solve the crash too.

I would say that libpng is a bit too finicky, when one considers that the files read fine everywhere else. Be that as it may ...

The problem is easy to fix. One need only load the offending PNG in The GIMP and export it as a new PNG. That ends the problem.

Unfortunately, finding the offending PNG file is a needle-in-the-haystack operation,when one considers that Volume 2 of the Dundjinni Archives contains 2+ GB of PNGs.

Servus,

Mark Oliva wrote: I would say that libpng is a bit too finicky, when one considers that the files read fine everywhere else. Be that as it may ...

Agreed, I found it very annoying too.

Mark Oliva wrote: The problem is easy to fix. One need only load the offending PNG in The GIMP and export it as a new PNG. That ends the problem.

Unfortunately, finding the offending PNG file is a needle-in-the-haystack operation,when one considers that Volume 2 of the Dundjinni Archives contains 2+ GB of PNGs.
Servus,

I confirmed with the png you attached that our current release candidate under test has no crashes or warnings. It should be out Tuesday.

Thank you!!

- Alejandro

Kanchou wrote:I confirmed with the png you attached that our current release candidate under test has no crashes or warnings. It should be out Tuesday.

Sounds good!

Servus,