NikoMar 23

hi there rust peeps

does anyone have any clue why a tokio runtime would have a hard cap on the number of tasks at 32,768?

hitting this limit silently fails to spawn new tasks and existing tasks hit "device or resource busy" errors when they need to use IO

no ulimits have been hit as far as i can tell (83 open files, well under limit of 16,384, and all other limits are either unlimited or unrelated to this issue)

given the failure mode is completely silent i have no clue where to start debugging this

Show threadsarah tonin Mar 23
@niko that's 1 + signed 16 bit max right ? probably an internal buffer indexed with that type then
Show threadNikoMar 23
@SRAZKVT well that's the problem i have zero clue where to start looking for limits like this
Show threadsarah tonin Mar 23
@niko debugger ? cargo rebuilds everything anyway, surely you can ask cargo to add debug info to deps too right ?
Show threadNikoMar 23
@SRAZKVT my config includes debug info yes but that still doesn't help because this is like finding a needle in a haystack with how big my codebase is
Show threadsarah tonin 
@niko minimal reproc ?
Mar 23 at 7:11amWeb