Fatal Crash, Unknown Error Code

[Zyliath]

Was playing Disco on the server, chilling in Pennsylvania while mining heavy water.

Suddently, while in the middle of mining an asteroid, the game froze and crashed with the error above.
Can someone lend me a hand here?

[Laz]

@Aingar from what I can tell, this seems to be part of some recursive logic of a nested element.

Code:

while ( *(_WORD *)(this + 26) )
  {
    v6 = *(_DWORD **)(this + 28);
    v7 = (void *)*v6;
    if ( *v6 )
    {
      sub_635C310(*v6);
      sub_6391D5A(v7);
    }
  }

`this+26` looks particularly suspect. sub_6391D5A is a free on the first item of v6.

@Zyliath Can you send me (or perhaps @Aingar is the better choice) the dump file?

---

[Zyliath]

@Aingar from what I can tell, this seems to be part of some recursive logic of a nested element.

Code:

while ( *(_WORD *)(this + 26) )
  {
    v6 = *(_DWORD **)(this + 28);
    v7 = (void *)*v6;
    if ( *v6 )
    {
      sub_635C310(*v6);
      sub_6391D5A(v7);
    }
  }

`this+26` looks particularly suspect. sub_6391D5A is a free on the first item of v6.

@Zyliath Can you send me (or perhaps @Aingar is the better choice) the dump file?

Can do one better: I can send the dump file to both of you, see if 2 heads work better than one.

---

"It's not a compliment, it's a matter of fact. I never saw you whining about stuff when it didn't go your way, you never do ooRP-arranged stuff, you're active, you're good at playing your character ingame and you're neutral enough to not end up as a clown infront of the community."

---

Character Table&Feedback Thread || Discovery Server and Forum Rules || Zyl's Art Database || Zyl's Fossils - Newbie posts

[Aingar]

The code crashes in the for loop above the segment you pasted Laz. Call stack for some reason shows nothing, but the stack itself The only thing I can tell is that this code is related to physics and collision states. Something must have went wrong when killing a collision group, but I can't fathom what went wrong as the system isn't reverse engineered at all.

Unless this crash is reliably reproducible I don't think we can fix this, pretty sure any attempts at ignoring the issue without crashing will simply end in a crash somewhere else (like it did for some other crash catch attempts we've made)

---