- Start factorio from vscode with debugger attached
- Load attached save or start new save
- Debugger catches assert error
- Game crashes to desktop
[2.1.12] Crash using debugger while save is being loaded after script assert
- protocol_1903
- Filter Inserter

- Posts: 539
- Joined: Fri Sep 09, 2022 4:33 pm
- Contact:
[2.1.12] Crash using debugger while save is being loaded after script assert
pYmod versions from git (just alienlife and dependents, mods attached. graphics mods not included, need to download from portal)
- Attachments
-
- factorio-current.log
- log file
- (157.16 KiB) Downloaded 39 times
-
- pY 2.1 porting.zip
- save file
- (851.84 KiB) Downloaded 36 times
-
- pyalienlife_3.1.3.zip
- (1.68 MiB) Downloaded 33 times
-
- pyindustry_3.1.2.zip
- (183.98 KiB) Downloaded 37 times
-
- pypetroleumhandling_3.1.1.zip
- (304.74 KiB) Downloaded 23 times
-
- pypostprocessing_3.1.3.zip
- (143.98 KiB) Downloaded 26 times
-
- pyrawores_3.1.2.zip
- (358.53 KiB) Downloaded 21 times
-
- pycoalprocessing_3.1.3.zip
- (387.59 KiB) Downloaded 23 times
pY and pYblock developer, wielder of fluid networks and subtick events in arbitrary ways. I make mods. Check them out, maybe.
https://mods.factorio.com/user/protocol_1903
Buy me a coffee
https://mods.factorio.com/user/protocol_1903
Buy me a coffee
-
justarandomgeek
- Filter Inserter

- Posts: 322
- Joined: Fri Mar 18, 2016 4:34 pm
- Contact:
Re: [2.1.12] Crash using debugger while save is being loaded after script assert
a quick look suggests this is the checkstack thing again, in another variation
-
justarandomgeek
- Filter Inserter

- Posts: 322
- Joined: Fri Mar 18, 2016 4:34 pm
- Contact:
Re: [2.1.12] Crash using debugger while save is being loaded after script assert
poking around at this some more trying to reconstruct the specific events - i have been unable to reproduce a crash now (and the checkstack fixes in 2.1.13 may very well have fixed it, iirc you said it was less reproducible after that), but more specifically what occurred is this:
1. while in a break for an error
2. one of your Watch Expressions (or possibly a hover/inline hint?) was evaluated
3. which looked up a global variable
4. which tripped your metatable to warn on undefined globals
5. which called debug.traceback
6. which segfaulted walking up the chain of CallInfos?!?!
if you do manage to reproduce it again, i would like to know all the active Watch Expressions, or better yet a dap trace log (trace:true in launch.json)
1. while in a break for an error
2. one of your Watch Expressions (or possibly a hover/inline hint?) was evaluated
3. which looked up a global variable
4. which tripped your metatable to warn on undefined globals
5. which called debug.traceback
6. which segfaulted walking up the chain of CallInfos?!?!
if you do manage to reproduce it again, i would like to know all the active Watch Expressions, or better yet a dap trace log (trace:true in launch.json)