Reassembly

Reassembly

View Stats:
Stack Overflow Error?
I wanted to play a bit of this game again, but twice now, for two different ships from two different factions, the game has closed itself without an error message. I was trying to save some of the prebuilt ships of the faction i was playing as to my fleet (selecting them, pressing 3, and alt-dragging the design to save it for later use in-game) In the log files it says:

INFO: found crash: [win32] Unhandled Top Level Exception
[DESERIALIZE] Lost 6 blocks making blueprint from '(null)': {{65563,""}=6}
OnTerminate begins (update thread): unhandled win32 exception
59.5 fps(iflip) 0.1 ups 81.1M
455522/400000 blocks 224 cl_pool
[win32] Unhandled Top Level Exception
[win32] Code: EXCEPTION_STACK_OVERFLOW, Flags: 0, PC: 0x00007FFFBB286FC8

(this one has 455522/400000 blocks, but the other has 341928/400000, if that means anything)

I don't know if this is caused by mods or not. I checked the mods I had installed and none of them updated or changed anything regarding the ship designs they had. I've never seen this error before, and I can't find any evidence that anyone else has, either, so that's why i didn't post it into the man bug report thread.

Any help would be appreciated.
Last edited by Lobsterperson; Aug 23, 2022 @ 3:41am
< >
Showing 1-2 of 2 comments
Blargo Aug 26, 2022 @ 8:13am 
In a nutshell, when a function in a program is executed, it is added to something called a "stack", and removed from that stack when it finishes executing. There is a limit to this stack, and a stack-overflow error is caused when that limit is passed.

There's a bunch of different ways this error can be created, but the most common way is making a recursive function, which just means to make a function re-execute itself.
There are valid reasons why one might make a recursive function, but if you're not careful, they can endlessly keep executing themselves and reach that stack limit quickly, since they never finish executing.

I'm going to take a wild guess and say that Reassembly maybe uses a recursive function for rendering blocks on a ship, and that 400000 block limit is the max stack limit.
Since you have a ship with 455522 blocks, It's exceeding that limit and causing the stack-overflow error.
Last edited by Blargo; Aug 26, 2022 @ 8:19am
Lobsterperson Aug 27, 2022 @ 7:00pm 
Originally posted by Dxpress:
In a nutshell, when a function in a program is executed, it is added to something called a "stack", and removed from that stack when it finishes executing. There is a limit to this stack, and a stack-overflow error is caused when that limit is passed.

There's a bunch of different ways this error can be created, but the most common way is making a recursive function, which just means to make a function re-execute itself.
There are valid reasons why one might make a recursive function, but if you're not careful, they can endlessly keep executing themselves and reach that stack limit quickly, since they never finish executing.

I'm going to take a wild guess and say that Reassembly maybe uses a recursive function for rendering blocks on a ship, and that 400000 block limit is the max stack limit.
Since you have a ship with 455522 blocks, It's exceeding that limit and causing the stack-overflow error.

That's strange. I don't think I've ever made or had a mod that includes ships that large. At the time of both crashes I was starting a new save with the factions, so there weren't any designs of mine that saved over. At the same time, if the error might be the amount of blocks in one ship being too high, how did it cause a crash of the same type that didn't exceed that limit? :<
< >
Showing 1-2 of 2 comments
Per page: 1530 50