[142] Crash drawing grid

0 favourites
From the Asset Store
Snap to visible grid - perfect solution for any game genre
  • I can also confirm a crash in V144.2 - 64bit following ramones simple example.

  • Problem Event Name:     APPCRASH

    Application Name:     Construct2.exe

    Application Version:     2.0.0.0

    Application Timestamp:     5237048f

    Fault Module Name:     StackHash_22da

    Fault Module Version:     6.1.7601.18229

    Fault Module Timestamp:     51fb164a

    Exception Code:     c0000374

    Exception Offset:     00000000000c4102

    OS Version:     6.1.7601.2.1.0.768.3

    Locale ID:     7177

    Additional Information 1:     22da

    Additional Information 2:     22da62097dc8c13a260fd1b8be6b9a98

    Additional Information 3:     db07

    Additional Information 4:     db07d627e13345a651902a765c4c89af

    And lets crash it again

    Problem Event Name:     APPCRASH

    Application Name:     Construct2.exe

    Application Version:     2.0.0.0

    Application Timestamp:     5237048f

    Fault Module Name:     StackHash_3566

    Fault Module Version:     6.1.7601.18229

    Fault Module Timestamp:     51fb164a

    Exception Code:     c0000374

    Exception Offset:     00000000000c4102

    OS Version:     6.1.7601.2.1.0.768.3

    Locale ID:     7177

    Additional Information 1:     3566

    Additional Information 2:     3566df989f77308e9def50045489207c

    Additional Information 3:     b697

    Additional Information 4:     b6972ee0d40a4c6050a1201af93c3227

    Generally StackHash errors can be fixed by turning off DEP for all programs and services that trigger the error.

    Unfortunetly, Construct 2 cannot be turned off (well the steam version) and You can't turn off a 64 bit .exe

    Ashley,

    Any ideas?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I've investigated further. I can reproduce on both Windows 7 and Windows 8 reliably, but only in release builds. When in a debug build, it does not occur. This is one of the most difficult classes of bug that can occur in software development. I have almost no leads from which to investigate. It's possible to debug release builds, but there is hardly any useful information (the debugger simply reports there may have been heap corruption, which is also another very difficult class of bug).

    Obviously this needs fixing and it may also be the source of other random crashes or instability in Construct 2, so I will keep working on it, but I don't know how long this could be around for. In the mean time I recommend trying to find workarounds (perhaps avoiding showing the grid?). I have also tried to add more useful information to the error messages for the next build, so let me know if any error messages change from r145+. On top of that any extra information such as which build the problem first started occurring in could be useful.

  • I have also tried to add more useful information to the error messages for the next build, so let me know if any error messages change from r145+. On top of that any extra information such as which build the problem first started occurring in could be useful.

    That is good news. Will definitely aid in narrowing it down a bit. This is truly a head scratch er, because it works perfectly, then doesn't without any changes to system, program, project file.

    A reboot fixes it - sometimes.

    If I open another project then open project with grid enabled it might work - sometimes.

    If I open capx of project it might work. Caproj of project crashes it almost always.

    Text alignment crashes it, but then doesn't.

    All, in all extremely weird, and agree, very hard to pin point.

  • I think I've finally managed to trace this to a VS2010 compiler optimizer bug. I've come up with a way to work around it and it no longer reproduces for me in a Windows 8 release build using ramones' reproduction steps. Hopefully this will also cover the other cases.

  • Ashley,

    Thank you the latest release R146 seems to have resolved this issue.

    Confirm it no longer reproduces for me on Windows 7

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)