Some problem with CuerLib?

[OucalGarlin]

Some players are experiencing a weird problem that might cause the game to crash (with CureLib, https://steamcommunity.com/sharedfiles/filedetails/?id=2900345009)

Every time the error message are totally different, but both of them include this: main_ex.lua(1226): RunCallbackInternal [INFO] - resources/scripts/main_ex.lua(1247): ? The creator of CureLib have no idea why is this happening. He doubts that RGON might be the reason of these error.

[jsgnextortex]

CuerLib doesnt require repentogon, try it without repentogon(using the -repentogoff launch param) see if the issue still persists or not. I'm curious why you decided to bring this issue here when the author themselves said that they doubt its a rgon issue tho, but I digreess.

[Cuerzor]

I'm the creator of this mod, I'd say the mainly strange point is that the line numbers in the crash reports in the console, like -20001760, and 51410378 in another picture. I wonder what's the reason?

[jsgnextortex]

That does look pretty damn fucked, yea, at the very reast the traceback is not being accurate there....do you have any scenario where we could reproduce this or is it completely random?

[Cuerzor]

Unfortunately, there is no stable method to reproduce it, and it is currently unknown why this problem occurred

[Cuerzor]

Also the guy who provided these issue pictures has recently replaced his PC and this issue are less frequent to happen. And these crashes are all have the same segment in log:

[INFO] - [C] (-1): xpcall [INFO] - resources/scripts/main_ex.lua(1226): RunCallbackInternal [INFO] - resources/scripts/main_ex.lua(1247): ?

Also there are 2 crashes caused by for iterator:

[INFO] - Lua stack trace: [INFO] - [C] (-1): for iterator [INFO] - ...xternal item descriptions_836319872/features/eid_api.lua(454): applyDescriptionModifier [INFO] - ...xternal item descriptions_836319872/features/eid_api.lua(429): getDescriptionObj [INFO] - ...item descriptions_836319872/features/eid_holdmapdesc.lua(469): ItemReminderAddDescription [INFO] - ...item descriptions_836319872/features/eid_holdmapdesc.lua(807): ItemReminderHandleItemPrinting [INFO] - ...item descriptions_836319872/features/eid_holdmapdesc.lua(522): ItemReminderHandleSelectedPassiveItem [INFO] - ...item descriptions_836319872/features/eid_holdmapdesc.lua(63): func [INFO] - ...item descriptions_836319872/features/eid_holdmapdesc.lua(842): ItemReminderGetDescription [INFO] - ...birth/mods/external item descriptions_836319872/main.lua(1584): ? [INFO] - [C] (-1): xpcall [INFO] - Caught exception, writing minidump...

[INFO] - Lua stack trace: [INFO] - [C] (-1): for iterator [INFO] - ...mods/!cuerlib_2900345009/cuerlib/class/helpers/table.lua(43): ? [INFO] - ...Rebirth/mods/!cuerlib_2900345009/cuerlib/class/grids.lua(419): GetPrevGridData [INFO] - ...h/mods/reverie_2538556220/scripts/grids/pebble_piles.lua(75): ? [INFO] - [C] (-1): xpcall [INFO] - resources/scripts/main_ex.lua(1226): RunCallbackInternal [INFO] - resources/scripts/main_ex.lua(1247): ? [INFO] - Caught exception, writing minidump...

And 1 crash caused by __gc:

[INFO] - Lua stack trace: [INFO] - [C] (-1): __gc [INFO] - [C] (-1): GetCollectibleRNG [INFO] - ...ebirth/mods/day dream all day/scripts/globalFunction.lua(346): ? [INFO] - ...ebirth/mods/day dream all day/scripts/globalFunction.lua(104): GetLibData [INFO] - .../mods/day dream all day/scripts/Items/SubmissionFlag.lua(187): ? [INFO] - [C] (-1): xpcall [INFO] - resources/scripts/main_ex.lua(1226): RunCallbackInternal [INFO] - resources/scripts/main_ex.lua(1247): ? [INFO] - Caught exception, writing minidump...

[Sylmir]

Do similar errors occur when users are handling other objects than grid entities ? Grid ents are notoriously fragile in Repentogon, so if we can narrow down the problem to them, it would help a lot.

If you have multiple logs available, do not hesitate to upload them all. The more information we have, the easier it will be to reproduce the problem

[Guantol-Lemat]

I've seen a similar issue (random crashes + incorrect lua stack traceback lines), caused by Intel Turbo Boost overclocking the CPU a little bit too much and causing a specific set of software (isaac included) to become unstable. Since you've mentioned the guy has replaced his PC recently, it might be worth looking into.

[Cuerzor]

Here, the error displayed in the console:

The code where it executed:

Then the game crashed:

Log file and dmp file: isaacv1.7.9b.J835-20250516-164046-56984-46380.dmp log.txt

[jsgnextortex]

Are these errors ocurring in code being called by setmetatable hooks?, theres seemingly a known lua issue where those can display the wrong lines in the traceback, specially when done in the __call indexes.

[Cuerzor]

Are these errors ocurring in code being called by setmetatable hooks?, theres seemingly a known lua issue where those can display the wrong lines in the traceback, specially when done in the __call indexes.

I do used metatable

[jsgnextortex]

I'd investigate those hooks specifically when looking for the source of these errors as, again, those can mess up the lua traceback for some odd reason....so the lines you see as the source of the error may not even be accurate.....granted, this would be an odd case, but not unprecedented. Overall, the use of setmetatable should be reduced to a minimum and the code thats excecuted though setmetatable __call hooks, specifically, should be given special attention. If you use those a lot, shit can get out of hand pretty quickly and debugging issues may become impossible. A thing to try would be to find a semi-reproduceable case and try commenting out the metatable hooks (which I assume are for mod compatibility) seeing if the issue persists. I'd assume there are true errors happening here, but the traceback info is just completely wrong.

[Busybody64]

Never happened to me, so I dunno....