Author Topic: OP2 Crash!  (Read 2058 times)

Offline Tellaris

  • Sr. Member
  • ****
  • Posts: 460
OP2 Crash!
« on: April 25, 2005, 01:42:24 AM »
Outpost 2 Crashed.
Memory Reference error.
I did debug of it
Attached is what C++ gave me.

I'm not sure if its me or OP2, but this has happend before, but never anywhere else...

I also posted this in wrong forum, please remove/move it.
Spell Checker!   The PoWeR tOoL
Click Here For Coolness
Self Proclaimed OPU Help desk.

Offline Leviathan

  • Hero Member
  • *****
  • Posts: 4055
OP2 Crash!
« Reply #1 on: April 25, 2005, 03:04:28 AM »
What were you doing to make it crash?

Offline Hooman

  • Administrator
  • Hero Member
  • *****
  • Posts: 4955
OP2 Crash!
« Reply #2 on: April 25, 2005, 10:03:02 AM »
Uhh, you just attached an older version of the SDK header file. (The one that was broken up into the files in the Outpost2DLL folder).

Do you have any more info on the crash?
« Last Edit: April 25, 2005, 10:03:25 AM by Hooman »

Offline Tellaris

  • Sr. Member
  • ****
  • Posts: 460
OP2 Crash!
« Reply #3 on: April 26, 2005, 01:58:25 AM »
Well.   This happend on Around The World.
I think it might be related to the "world view" button, but cannot be completely sure.   Pushing this button HAS resulted in the game just simply quitting though, so chances are this is related.
Spell Checker!   The PoWeR tOoL
Click Here For Coolness
Self Proclaimed OPU Help desk.

Offline Leviathan

  • Hero Member
  • *****
  • Posts: 4055
OP2 Crash!
« Reply #4 on: April 26, 2005, 02:20:52 AM »
Ah yes, you said that has crashed it before a few times, ive never experienced it, but there are many things which can crash op2.

Offline BlackBox

  • Administrator
  • Hero Member
  • *****
  • Posts: 3093
OP2 Crash!
« Reply #5 on: April 26, 2005, 07:32:43 PM »
perchance it has to do with memory allocation errors. I'm not sure where the code is that deals with the globe view, but I could see it allocating extra memory for that (or referencing invalid extra memory). Maybe it assumes that a GlobalAlloc call wouldn't fail. lol. I've never seen the code though so it could be a number of problems.

I've never had that problem though either, so I couldn't reproduce it.