Indexing a non-existant component type stack overflows instead of returning nothing #33

Closed
opened 2025-07-27 16:31:18 +00:00 by Ponali · 3 comments
Ponali commented 2025-07-27 16:31:18 +00:00 (Migrated from github.com)
Image
<img width="627" height="487" alt="Image" src="https://github.com/user-attachments/assets/0b4c9d26-5a6c-43db-bb75-2d82d21bff4f" />
WahPlus commented 2025-07-27 16:31:59 +00:00 (Migrated from github.com)

I don't even...th- that's not even a Lua error??? What am I supposed to do about that?????

I don't even...th- that's not even a Lua error??? What am I supposed to do about that?????
Ponali commented 2025-07-27 16:35:51 +00:00 (Migrated from github.com)

It is possible to make a C stack overflow error simply from some Lua code.
Just repeating a function would return stack overflow, but if it takes something from the metatable, it returns a C stack overflow error.

Image Image
It is possible to make a `C stack overflow` error simply from some Lua code. Just repeating a function would return `stack overflow`, but if it takes something from the metatable, it returns a `C stack overflow` error. <img width="608" height="494" alt="Image" src="https://github.com/user-attachments/assets/ce8ab4c6-3abd-4373-b833-aa85340f6ebc" /> <img width="758" height="519" alt="Image" src="https://github.com/user-attachments/assets/f6b5b432-942c-4dba-918b-ae2c6bdd0785" />
WahPlus commented 2026-06-15 16:38:02 +00:00 (Migrated from github.com)

Fixed in 317c0df9e8

Fixed in 317c0df9e8d1a32650749f82aedb5d6511a1233e
Sign in to join this conversation.