Kerbal Space Program

Sorry for the screwed up formatting, I have no idea how that happened...

a.g. wrote:

This means that until fixed/patched the 64-bit build will crash whenever it loads a png image that uses one of the optimized code paths, and the relevant buffers are not within the low 2 GB of the address space (which depends on kernel & library settings, and chance).

This does not explain why the 32-bit version also crashes like that though.

You didn't post the Player.log for the 32-bit version - it actually contains some useful stack traces.

Btw, for the last 2 days I've been running with KSP.x86_64 where I changed bytes 7cebc7 and 7cebcc from 01 to 00 so as to make png_mmx_support from that pnggccrd.c always return 0, and that seems to have solved the crash I was having.

Now it seems both crash in the fglrx stuff - can't help there unfortunately.

This problem is also happening in Linux Mint 15 which is using the Ubuntu Raring repos for the libraries in question. Thus the problem is also appearing on Ubuntu and Ubuntu spinoffs.

Just because the distro isn't supported doesn't mean this isn't worthy if the problem can be traced back to a dependency as was traced here. This is a problem caused by the library, not the distro.

If need be I can pop Ubuntu Raring on a virtual machine just to prove that this isn't a distro specific problem.

I tried it, and I get the same crashes. The 32-bit version crashes just as early as before. The 64-bit version also crashes like before. Since I do not know the proper offset for the png fix for the 64-bit edition of the new version, I can not properly test that partial workaround. I'm not super-keen on trying to reverse engineer x86 assembly.

Worth noting is that my computer setup changed since I originally filed the bug, I now run a dual monitor setup (24" 1920x1200 + 22" 1680x1050). Other than that, it is the same.

Does it occur without the flgrx drivers?

Yes, in all cases I'm using fglrx. (Sorry for the slow response, I have been on a trip without internet for the past 8 days.) Driver version is still 1:12-6+point-3 according to the package manager.

The way I read his report, it's an issue with debian-derivitives distributing a library which has been incorrectly compiled. I'm not sure if Squad can do anything here, it's an upstream issue.

I've just checked both the debian and ubuntu bugtrackers for libpng-12, and both don't seem have any open issues that correlate with a.g.s deductions. I'd recommend pursuing this issue with the distros, as KSP cannot be the only one affected by such an issue.

(unless of course I'm reading this wrong, and the culprit isn't a libpng.so, but a .a library that got statically compiled into unity, in which case unity should get petitioned to clean up its compilation environment).

Well, since the patch is for the main ksp executable, it follows that it is indeed a statically linked library in unity. ;)

It would be interesting to see if this is fixed in the next release, which apparently would use a new unity version, unlike all the releases from 0.20.2 to 0.22.