node assertion - possible race condition about landspeed.js HOT 3 CLOSED

This might be happening because node/v8 tries to GC the object while it's still being used. This could happen when the calls to Ref() and Unref() aren't balanced. I just looked through the C++ code the server calls but I didn't see any apparent misuse there.

On the other hand—and I believe this is more likely—this may not be node or node-mapnik related: Perhaps something in mapnik causes a buffer overflow which overwrites a malloced section and the metadata it put there. When node-mapnik tries to properly deallocate an object, it can't find the associated metadata anymore, making free() fail.

from landspeed.js.

This looks more and more like a buffer overflow; the assertion in that line shouldn't fail from Ref/Unref misuse; only when data is corrupted.

from landspeed.js.

No longer seeing this - assuming it was an old Node.js 0.4.x bug.

from landspeed.js.