Tilemap - crash if y-sort active and tiles at 512x512 or more

[zzz-assault]

Godot version:

• 3.1.1 (64 bit) - 2D

Remark: the 32 bit client seems to be able to achieve higher tile number, before he simply stopps to respond

OS/device including version:

• Windows 10
• RTX 2080
• I7 8700

Issue description:
If a tilemap is filled by GD-Script, exceeds 512x512 tiles and has y-sort active it crashes with the following error message.

• ERROR: _get_socket_error: Socket error: 10054
• At: drivers/unix/net_socket_posix.cpp:190

Additional remark: The memory usage gets significantly higher with y-sort active.

Steps to reproduce:
The attached project already has the correct setup -> if you remove y-sort it runs without crash.
But you can also just load via code a tilemap with double loop … error only occurs if y-sort is active.

Minimal reproduction project:
project.zip

[Zireael07]

Socket error 10054 is just a generic debugger crashed error.

Are you using remote screne tree? How high is the memory usage when it crashes? IIRC Godot can't handle memory use bigger than 2 GB...

[zzz-assault]

I know, but in this case, it's super clear - as soon as I turn y-sort off, it works without any issue.

Memory usage (in the attached simple sample project) at 450x450 is the following.

y-sort = on

y-sort = off

I can't assume that the Memory usage at 512x512 would be significantly higher, but unfortunately the debug monitor doesn't show reliable data after the crash.

Edit: No "remote screne tree" usage in the sample project it's just a tilemap with tileset, which is loaded via GD-script double for loop and set_cell … super basic … :)

[qarmin]

Godot crashing when allocating memory with alloca