22.8 one more time

[bob]

If you have downloaded 22.8, please do so again. I have a script to move files around, and I just discovered that one of the "stages" did not work due to a software issue dealing with .ssh public/private key issues. As a result, the 22.8 source I released yesterday is missing the "memory leak fix" from 22.7. If you prefer, you can simply use init.c and thread.c from 22.7, which did not change in 22.8, and that will solve the issue the same as if you re-download 22.8. I believe this glitch has been fixed. My scripts are intentionally "silent" when they move files around to avoid tons of output, but I did not let any "error messages" leak out either so I did not notice that one set of SCP's was failing. .

I believe I have this fixed so that it won't happen again. It has caused me a lot of unnecessary debugging and re-writing fixes that were lost over the past couple of weeks...

[glorfindel]

Thanks. Perhaps you can use some version control system in order to track changes easier. Especially since you are making changes to the source code from many places and many developers have access to the source sode.

[bob]

Thanks. Perhaps you can use some version control system in order to track changes easier. Especially since you are making changes to the source code from many places and many developers have access to the source sode.

I am looking for a relatively simple solution that will work in the environment I am using for development.

[Jim Ablett]

If you have downloaded 22.8, please do so again. I have a script to move files around, and I just discovered that one of the "stages" did not work due to a software issue dealing with .ssh public/private key issues. As a result, the 22.8 source I released yesterday is missing the "memory leak fix" from 22.7. If you prefer, you can simply use init.c and thread.c from 22.7, which did not change in 22.8, and that will solve the issue the same as if you re-download 22.8. I believe this glitch has been fixed. My scripts are intentionally "silent" when they move files around to avoid tons of output, but I did not let any "error messages" leak out either so I did not notice that one set of SCP's was failing. .

I believe I have this fixed so that it won't happen again. It has caused me a lot of unnecessary debugging and re-writing fixes that were lost over the past couple of weeks...

Updated Crafty 22.8 Windows builds with memory leak fix.

http://www.mediafire.com/?zyumnmynnge

Jim.

[Charles B.]

Presently Peter Skinner's site has the date of the page update as being December 1, 2008. Checking the modified date in one of the Crafty engine properites box shows a modified date of December 2, 2008. So Mr. Skinner's executables have been brought up to the present 22.8 fixes, too?

http://www.webkikr.net/

[Jim Ablett]

Presently Peter Skinner's site has the date of the page update as being December 1, 2008. Checking the modified date in one of the Crafty engine properites box shows a modified date of December 2, 2008. So Mr. Skinner's executables have been brought up to the present 22.8 fixes, too?

http://www.webkikr.net/

Hi Charles,

Yes. Just downloaded/tested and working correctly - no memory leak

Jim.