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.