Coroutine.create can hide callstack information when requiring by id

Bug Reports Engine Bugs
,
1

Using require in a coroutine on a remote asset uploaded with MainModule can hide the callstack for where the require was called.
This seems to happen with functions that are implemented on the C-side of Luau (for example, functions that return “[C]” when using debug.info(func, 's'))

For example, if I upload a ModuleScript named ‘MainModule’ with the following source–

print('Hello World!')
return 0

–and I require the asset id using a coroutine in a server script–

local thread = coroutine.create(require)
coroutine.resume(thread, 107462162251037)

–then the require callstack seems to vanish.
image

The module has distribution enabled if you would like to use mine instead of uploading your own module to test it.

System Info (If needed):
CPU: AMD Ryzen 7 7800X3D 8-Core Processor
RAM: 64 GB
GPU: NVIDIA GeForce RTX 4070

2

This is working as intended - each coroutine has its own call stack.

3

Oh, alright! I was just worried about this becoming abused because some people might see that there’s a mysterious require and they wouldn’t see where it was coming from but I assume that they can click on an output in studio to find its source now that I think about it