This just happened to me.
It was working fine for several days, I’m up to Y21. Last play session the only different thing I did, besides the usual games, research and training, was create the Research Lab and start a project.
I get the error popup and the game is pretty much frozen.
I was on 1.3.2 and already tried 1.3.5, error still happening
2007 iMac running 10.7.5
i have the 1.3.5 version and still crashes when i try to load
Same issue here.
Game Version 1.3.5. Happened first when I entered Game Stage 3.
When I open the game it says “Click to continue”. Then the loading bar appears for a short time and then the game crashed without any error message.
Macbook 15" Retina Mid 2012. OS X 10.8.3
The following messages appear in the console when I open the game:
03.05.13 18:00:56,536 WindowServer[92]: CGXRegisterWindowWithSystemStatusBar: window 1b already registered
03.05.13 18:00:59,440 WindowServer[92]: CGXGetConnectionProperty: Invalid connection 84123
03.05.13 18:00:59,440 WindowServer[92]: CGXGetConnectionProperty: Invalid connection 84123
03.05.13 18:00:59,440 WindowServer[92]: CGXGetConnectionProperty: Invalid connection 84123
03.05.13 18:00:59,440 WindowServer[92]: CGXGetConnectionProperty: Invalid connection 84123
03.05.13 18:00:59,441 WindowServer[92]: CGXGetConnectionProperty: Invalid connection 84123
03.05.13 18:00:59,739 ReportCrash[586]: Saved crash report for node-webkit Helper[583] version 26.0.1377.0 (1377.0) to /Users/myusername/Library/Logs/DiagnosticReports/node-webkit Helper_2013-05-03-180059_Sebs-MacBook.crash
The crash report says the following:
Process: node-webkit Helper [583]
Path: /Applications/Game Dev Tycoon.app/Contents/Frameworks/node-webkit Helper.app/Contents/MacOS/node-webkit Helper
Identifier: com.intel.nw.helper
Version: 26.0.1377.0 (1377.0)
Code Type: X86 (Native)
Parent Process: node-webkit [581]
User ID: 501
Date/Time: 2013-05-03 18:00:59.327 +0200
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Crashed Thread: 0 CrRendererMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
–> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] —/--- SM=NUL /Applications/Game Dev Tycoon.app/Contents/Frameworks/node-webkit Helper.app/Contents/MacOS/node-webkit Helper
VM_ALLOCATE 0000000000001000-00000000000c7000 [ 792K] —/--- SM=NUL
Thread 0 Crashed:: CrRendererMain Dispatch queue: com.apple.main-thread
0 node-webkit Framework 0x01b7910b 0xcc000 + 27971851
1 node-webkit Framework 0x00f545b9 0xcc000 + 15238585
2 node-webkit Framework 0x01409c78 0xcc000 + 20175992
3 node-webkit Framework 0x013f48f9 0xcc000 + 20089081
4 node-webkit Framework 0x013f1574 0xcc000 + 20075892
5 node-webkit Framework 0x013f0a6e 0xcc000 + 20073070
6 node-webkit Framework 0x01401e4b 0xcc000 + 20143691
7 node-webkit Framework 0x01404aab 0xcc000 + 20155051
8 node-webkit Framework 0x013c777d 0xcc000 + 19904381
9 node-webkit Framework 0x0071ba35 0xcc000 + 6617653
10 node-webkit Framework 0x00349292 0xcc000 + 2609810
11 node-webkit Framework 0x0034d6b2 0xcc000 + 2627250
12 node-webkit Framework 0x0034aa88 0xcc000 + 2615944
13 node-webkit Framework 0x0034a87f 0xcc000 + 2615423
14 node-webkit Framework 0x00365a9a 0xcc000 + 2726554
15 node-webkit Framework 0x003597a2 0xcc000 + 2676642
16 node-webkit Framework 0x0035f053 0xcc000 + 2699347
17 node-webkit Framework 0x007cc440 0xcc000 + 7341120
18 node-webkit Framework 0x016896ad 0xcc000 + 22795949
19 node-webkit Framework 0x00b56433 0xcc000 + 11052083
20 node-webkit Framework 0x00b570f9 0xcc000 + 11055353
21 node-webkit Framework 0x00b55fc0 0xcc000 + 11050944
22 node-webkit Framework 0x000cd999 ContentMain + 41
23 com.intel.nw.helper 0x000c7f75 0xc7000 + 3957
Thread 1:
0 libsystem_kernel.dylib 0x9754b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x975ac0ac _pthread_workq_return + 45
2 libsystem_c.dylib 0x975abe79 _pthread_wqthread + 448
3 libsystem_c.dylib 0x97593d2a start_wqthread + 30
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9754b9ae kevent + 10
1 libdispatch.dylib 0x9533bc71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x9533b7a9 _dispatch_mgr_thread + 53
Thread 3:
0 libsystem_kernel.dylib 0x9754b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x975ac0ac _pthread_workq_return + 45
2 libsystem_c.dylib 0x975abe79 _pthread_wqthread + 448
3 libsystem_c.dylib 0x97593d2a start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x9754b9ae kevent + 10
1 node-webkit Framework 0x002540dd 0xcc000 + 1605853
2 node-webkit Framework 0x0079bf9b 0xcc000 + 7143323
3 node-webkit Framework 0x00240fcd 0xcc000 + 1527757
4 libsystem_c.dylib 0x975a95b7 _pthread_start + 344
5 libsystem_c.dylib 0x97593d4e thread_start + 34
Thread 5:: VC manager
0 libsystem_kernel.dylib 0x9754a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x975ae280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x97634095 pthread_cond_wait$UNIX2003 + 71
3 node-webkit Framework 0x007f1093 0xcc000 + 7491731
4 node-webkit Framework 0x007f1d3b 0xcc000 + 7494971
5 node-webkit Framework 0x007f1b42 0xcc000 + 7494466
6 node-webkit Framework 0x007d21fc 0xcc000 + 7365116
7 node-webkit Framework 0x007ce031 0xcc000 + 7348273
8 node-webkit Framework 0x007e656e 0xcc000 + 7447918
9 node-webkit Framework 0x007cd76a 0xcc000 + 7346026
10 node-webkit Framework 0x007fded1 0xcc000 + 7544529
11 node-webkit Framework 0x007fdf6d 0xcc000 + 7544685
12 node-webkit Framework 0x007f8cd9 0xcc000 + 7523545
13 libsystem_c.dylib 0x975a95b7 _pthread_start + 344
14 libsystem_c.dylib 0x97593d4e thread_start + 34
Thread 6:: SamplerThread
0 libsystem_kernel.dylib 0x9754880e semaphore_wait_trap + 10
1 node-webkit Framework 0x0241576b v8::internal::MacOSSemaphore::Wait() + 27
2 node-webkit Framework 0x022f4ddc v8::internal::RuntimeProfiler::WaitForSomeIsolateToEnterJS() + 140
3 node-webkit Framework 0x02415855 v8::internal::SamplerThread::Run() + 85
4 node-webkit Framework 0x02414f05 0xcc000 + 36998917
5 libsystem_c.dylib 0x975a95b7 _pthread_start + 344
6 libsystem_c.dylib 0x97593d4e thread_start + 34
Thread 7:: MediaPipeline
0 libsystem_kernel.dylib 0x9754a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x975ae280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x97634095 pthread_cond_wait$UNIX2003 + 71
3 node-webkit Framework 0x007f1093 0xcc000 + 7491731
4 node-webkit Framework 0x007f1d3b 0xcc000 + 7494971
5 node-webkit Framework 0x007f1b42 0xcc000 + 7494466
6 node-webkit Framework 0x007d21fc 0xcc000 + 7365116
7 node-webkit Framework 0x007ce031 0xcc000 + 7348273
8 node-webkit Framework 0x007e656e 0xcc000 + 7447918
9 node-webkit Framework 0x007cd76a 0xcc000 + 7346026
10 node-webkit Framework 0x007fded1 0xcc000 + 7544529
11 node-webkit Framework 0x007fdf6d 0xcc000 + 7544685
12 node-webkit Framework 0x007f8cd9 0xcc000 + 7523545
13 libsystem_c.dylib 0x975a95b7 _pthread_start + 344
14 libsystem_c.dylib 0x97593d4e thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x0bdb3400 ecx: 0xffffffff edx: 0x055abd20
edi: 0x055cce0c esi: 0x055cce0c ebp: 0xbff389d8 esp: 0xbff389d0
ss: 0x00000023 efl: 0x00010282 eip: 0x01b7910b cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000000
Logical CPU: 5
Having this issue while starting the game, not even getting a menu or anything, it just crashes right off the bat… Made a thread about it, cause i thought it was a different issue as it has nothing to do with savegames… ( [Mac] Crash on startup KERN_PROTECTION_FAILURE ). If not, great… i’ll follow this thread until a fix is found.
That would be the best. Your issue might be related to the overall game load issue, since it seems to be the same crash cause (it’s at address 0 which is identical to the person above you) and therefore could be caused by the same reason as everyone else’s. If the patch doesn’t work for you, I’ll happily reopen your individual thread. They just seemed far too similar to not combine. 
Sure, no problem, just wasn’t sure about it. Looking forward to a fix, i’ll try 1.3.5 now and see if this helps in any way.
I’ll also try on my other Mac at home (10.8.x, this one is 10.7.2), if it works on that one, i’ll report it, might help in tracking down the specifics of the bug.
EDIT: 1.3.5 produces the same error right at start
I’m still getting the crash in 1.3.5
1.3.5 only fixed the music issue. 1.3.4 should have fixed the DOM Exception but not the crash.
+@straks
same problem for long time
Your codeNw.js workaround didn’t work for me. But I had already updated to 1.3.5 before I tried it. Too bad.
We are very sorry for your troubles. We are investigating this issue non stop (good that we are living on different continents) and hopefully we can provide a fix soon.
I believe if I don’t close the game, I can continue playing indefinitely. Can anyone else confirm this? If so, the temporary solution is to minimize the game and never close it.
Also, is there any data I can provide to the developers? Should I share my file__0.localstorage file? Are there any log files I can dig up or genrate for you to help?
In case it can help here is my entire “Application Support/Game Dev Tycoon folder”.
http://brianhanifin.com/drop/gdt-appsupport-201305031138.zip
One more thought. Could the problem be caused by the game history being too long? Or perhaps another field in the sqlite database being too long for the game engine to parse? If so, can we edit our save files to remove some of the older game entries?
@DanielKlug, I would think this type of game draws primarily technically savvy users. Some of us have done some development work in the past. I for one am really enjoying the game… and for the price I don’t mind some hiccups. I figure I was about due to start a new game company anyway. 
Could the error be caused by characters in our game names? I have used characters like : , & . and ?* in my game names.
For example:
Why as a customer i have to come in the Forum read everything go back to my email, re upload everything and nothing work even after all effort…
Minus 1 FAN here
I give you 2 out of 10 -Terrible bug in the game, not ready yet, waste of my money.
Good lord, it’s 2013 can you at least do Auto Update !
I don’t care if it’s 10$ or 60$ i pay for the game. Im legit i don’t pirate your stuff and i get screw even if i give my money…
Now go Bankrupt
Guess you meant download. Well … if NOTHING works you must be a ghost, at least breathing should work. Your PC/Mac should work too since you used email … could have been a smartphone though so maybe I’m mistaken.
Do you even read what you write? You expect the same from a $10 game as from a $60 dollar game? Seriously? shakes head
I smell the troll in you…
If my english is not good enough for you… go learn a 2nd language and came back after !
In the real world, nothing is bug-free. This issue comes up when you load a save file pretty late in the game, it seems. Auto-update would do diddly squat right now because you probably don’t get far enough in game to get an update anyway.
If you want to play the game, you are more than able to. If your game crashes when loading a save file, then you can delete the file and start from scratch, or simply wait until there is a fix.
You can’t really ask for much more when the response is that they’re investigating the reason. Unlike inside the game, a patch isn’t as easy as clicking on someone and choosing “make patch”.
seems we are finally making some good progress with this. while I cannot say if this will fix every startup crash, we tested a couple of savegames and they work now. we are still testing the release but plan to update it later today.
How long will I have to wait?