Terrain generated by Lua mapgen destroys itself

[SmallJoker]

A weird issue which was added between the commits
3fa4f78
and
f3eefeb

Before those commits:
http://imgur.com/QdjZ3rl

After those commits:
http://imgur.com/zOrcc07
http://imgur.com/sN1zB2n

Windows XP SP3 32-bit
All new builds contain this bug
The terrain gets generated and deleted (set to air) afterwards (sometimes visible in-game and in the log of the mapgen)

[Zeno-]

I have a similar (or the same) issue on Linux. In my case it seems that the voxelmanip nodes are set momentarily and then revert to whatever the node was beforehand (e.g. default:stone).

[kwolekr]

Hi guys, does this issue happen with the current HEAD?

[SmallJoker]

I found a possible fix for this bug.

My mapgen skips with a setting all already generated areas. When I disable this setting, everything works fine.

This is what I mean by "skip":

local lastPos = {x=6.66,y=6.66,z=6.66}

minetest.register_on_generated(function(minp, maxp, seed)
    if vector.equals(minp, lastPos) then
        print("Skipped "..minetest.pos_to_string(minp))
        return
    end
    ...
end)

It worked fine before those 3 commits appeared.