[0.12.6] [Mac OSX] [Martin] [pending] Freeze on application start

[gnz]

When starting Factorio the application sometimes freezes ( i.e. beachballs ). This seems to happen around half of the time and then there is nothing to do than force quit and restart Factorio and hope for better luck.

As far as I can tell, the only errors that show up are the following:

Code: Select all

2015-02-04 10:32:59.669 factorio[63983:2915225] NSWindow warning: adding an unknown subview: <NSView: 0x104a26070>
2015-02-04 10:32:59.671 factorio[63983:2915225] Call stack:
(
	0   AppKit                              0x00007fff8e773a9c -[NSThemeFrame addSubview:] + 107
	1   AppKit                              0x00007fff8e0c734e -[NSView replaceSubview:with:] + 153
	2   AppKit                              0x00007fff8e87d3f9 __60-[NSView(NSFullScreenMode) enterFullScreenMode:withOptions:]_block_invoke + 159
	3   AppKit                              0x00007fff8e1aa9b5 NSPerformWithScreenUpdatesDisabled + 65
	4   AppKit                              0x00007fff8e87d2f2 -[NSView(NSFullScreenMode) enterFullScreenMode:withOptions:] + 2972
	5   factorio                            0x00000001006a6d66 -[ALOpenGLView enterFullScreenWindowMode] + 166
	6   Foundation                          0x00007fff8adb1f4c __NSThreadPerformPerform + 293
	7   CoreFoundation                      0x00007fff8cf1d661 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	8   CoreFoundation                      0x00007fff8cf0f7ed __CFRunLoopDoSources0 + 269
	9   CoreFoundation                      0x00007fff8cf0ee1f __CFRunLoopRun + 927
	10  CoreFoundation                      0x00007fff8cf0e838 CFRunLoopRunSpecific + 296
	11  HIToolbox                           0x00007fff8d3a743f RunCurrentEventLoopInMode + 235
	12  HIToolbox                           0x00007fff8d3a71ba ReceiveNextEventCommon + 431
	13  HIToolbox                           0x00007fff8d3a6ffb _BlockUntilNextEventMatchingListInModeWithFilter + 71
	14  AppKit                              0x00007fff8e0b26d1 _DPSNextEvent + 964
	15  AppKit                              0x00007fff8e0b1e80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
	16  AppKit                              0x00007fff8e0a5e23 -[NSApplication run] + 594
	17  factorio                            0x00000001006a512b _al_osx_run_main + 1675
	18  factorio                            0x00000001007ce970 main + 16
	19  factorio                            0x0000000100001214 start + 52
)

I suspect that this is actually the problem given that when it locks up then one of the three windows that Factorio spawns does not have the usual window title ( i.e. "Factorio 0.11.15" in this case ). It's a bit hard to see but here are two screenshots of that:


Given that it goes through ALOpenGLView then it's likely an Allegro bug, but unless it's only on my machine then it should probably be adressed before the stable version.

[gnz]

Further to this, starting Factorio in windowed mode does not have any of these problem which makes me think that it's related to the ordering of the fullscreen outlet.

[ssilk]

I see some similarities to this https://forums.factorio.com/forum/vie ... f=7&t=8446

I saw, that Factorio is opening three windows, one with full white, as above, one with full black and the full screen game window. Maybe it's just that, we cannot get focus to the game window, cause the others are above.

[gnz]

I see some similarities to this https://forums.factorio.com/forum/vie ... f=7&t=8446

I saw, that Factorio is opening three windows, one with full white, as above, one with full black and the full screen game window. Maybe it's just that, we cannot get focus to the game window, cause the others are above.

This is almost certainly related. It's not so much focus in the sense of putting that window on top in the window manager, but certainly focus in the sense that the app seems to be talking to the wrong window while drawing in another etc. Some form of racing condition because of the way the full screen is initialised is likely, but it could also be an Allegro bug but I see no mention on their project page about this.

[kovarex]

Does it still happen in 0.12.6?

Can you show the log from 0.12.6 when this happens?

What is your hardware configuration.

[Quis]

I *think* I experience the same bug. Running on 0.12.6 on Mac OS X 10.10.5 here. When I start the game it loads and sometimes (but sometimes not!) I get the spinning beach ball and the game will hang.

This is the complete log output as shown when started from the commandline:

Code: Select all

   0.000 2015-09-05 15:23:08; Factorio 0.12.6 (Build 16640, mac)
   0.000 Operating system: Mac OS X 10.10.5
   0.000 Program arguments: "/Applications/factorio 0.12.app" 
   0.000 Read data path: /Applications/factorio 0.12.app/Contents/data
   0.000 Write data path: /Users/quis/Library/Application Support/factorio
   0.000 Binaries path: /
2015-09-05 15:23:08.915 factorio[83716:750337] NSWindow warning: adding an unknown subview: <NSView: 0x101b74970>
2015-09-05 15:23:08.918 factorio[83716:750337] Call stack:
(
	0   AppKit                              0x00007fff951e454d -[NSThemeFrame addSubview:] + 107
	1   AppKit                              0x00007fff952157ce -[NSView replaceSubview:with:] + 153
	2   AppKit                              0x00007fff959fd379 __60-[NSView(NSFullScreenMode) enterFullScreenMode:withOptions:]_block_invoke + 159
	3   AppKit                              0x00007fff9528ebdb NSPerformWithScreenUpdatesDisabled + 65
	4   AppKit                              0x00007fff959fd272 -[NSView(NSFullScreenMode) enterFullScreenMode:withOptions:] + 2972
	5   factorio                            0x00000001007e1fc6 -[ALOpenGLView enterFullScreenWindowMode] + 166
	6   Foundation                          0x00007fff874badd0 __NSThreadPerformPerform + 293
	7   CoreFoundation                      0x00007fff8d56da01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	8   CoreFoundation                      0x00007fff8d55fb8d __CFRunLoopDoSources0 + 269
	9   CoreFoundation                      0x00007fff8d55f1bf __CFRunLoopRun + 927
	10  CoreFoundation                      0x00007fff8d55ebd8 CFRunLoopRunSpecific + 296
	11  HIToolbox                           0x00007fff8c04156f RunCurrentEventLoopInMode + 235
	12  HIToolbox                           0x00007fff8c0412ea ReceiveNextEventCommon + 431
	13  HIToolbox                           0x00007fff8c04112b _BlockUntilNextEventMatchingListInModeWithFilter + 71
	14  AppKit                              0x00007fff952338ab _DPSNextEvent + 978
	15  AppKit                              0x00007fff95232e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
	16  AppKit                              0x00007fff95228af3 -[NSApplication run] + 594
	17  factorio                            0x00000001007e040b _al_osx_run_main + 1675
	18  factorio                            0x000000010090a010 main + 16
	19  factorio                            0x00000001000011e4 start + 52
)
   0.596 Initialised OpenGL: Intel HD Graphics 5000 OpenGL Engine; driver: 2.1 INTEL-10.6.33
   0.986 Graphics options: [FullScreen: true] [VSync: true] [UIScale: 100%] [MultiSampling: OFF] [Graphics quality: normal] [Video memory usage: all] [Screen: 255]
   1.033 Loading mod core 0.0.0 (data.lua)
   1.039 Loading mod base 0.12.6 (data.lua)
   1.704 Initial atlas bitmap size is 16384
   1.707 Created atlas bitmap 16384x7661
  15.474 Factorio initialised

HW config:
MacBook Air (13-inch, Early 2014)
1.7 GHz Intel Core i7
8 GB 1600 MHz DDR3
Intel HD Graphics 5000 1536 MB

[Quis]

If i change my config to start in windowed mode (instead of full screen) the game starts normally. I did see this error when clicking Exit, though:

Code: Select all

2015-09-05 15:27:33.346 factorio[83776:753157] void *NSMapGet(NSMapTable *, const void *): map table argument is NULL
  17.152 Goodbye

[clouths]

This bug occurs when you build an app on OSX 10.10 and run it under 10.10 as well.

Apple fixed this issue on OSX 10.11 based on this article. (In the NSWindow section)

I think I found a fix (that can be solved only with a new build) here.

I hope this can help!

[HanziQ]

The latest releases were built on 10.11, is this still happening?