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 threadEdvin MalinovskisMar 23
@niko looking at where tokio uses i16 internally could be a start
Show threadNiko
@nCrazed hmm true i’ll do that in the morning thanks for the idea
Mar 23 at 10:14amWeb