widelands-dev team mailing list archive

[kaputtnik <somal@xxxxxxxx>]

As i understand the "double free or corruption (!prev)" failure happens because of trying to free memory which is already been freed former.

And i have the feeling that the crash is mostly triggered when much memory (RAM) is consumed/newly assigned through some other programs. So i tried to consume/assign much memory by open all widelands screenshots in Gimp and let widelands run from trunk. Starting this branch and click on the help in editor causes widelands to crash with the known error message. But starting it again all is fine. Yesterday the error is triggered after starting blender and afterwards starting this branch. And again the error is only triggered once. So there is no real scenario for testing, but assigning new memory seems to trigger the error more often than starting with always the same amount of memory usage.
-- 
https://code.launchpad.net/~widelands-dev/widelands/lua-driven-help/+merge/289782
Your team Widelands Developers is subscribed to branch lp:~widelands-dev/widelands/lua-driven-help.