Page 1 of 2
Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Thu Oct 27, 2016 3:42 pm
by RARaines
Here's how I'm generating the error. I click the T-Engine icon to start the app. The window opens but it displays all black and sits there.
I have attached the log. BTW, I am trying to run the new version of Tome, 1.4.9.
I've done a number of fresh installs, but with no success.
Thanks,
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Thu Oct 27, 2016 11:28 pm
by RARaines
I've also experimented around and find that TE4 1.4.8 still works.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Fri Oct 28, 2016 12:56 am
by effable
I'm having the same problem with 1.4.9 under OS 10.12.1 -- it displays a black window, but then does nothing else even though it seems to peg one CPU core indefinitely.
The system.log says this when I launch the app:
Code: Select all
Oct 27 17:40:29 mycomputer T-Engine[1774]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
Then again, since it says the same thing when I successfully launch 1.4.8, I don't know it that is particularly helpful.
There are some "System Reports" log entries for the 1.4.9 app, but it doesn't appear to generate them every time. If you think they'd be helpful let me know and I'll post one.
FWIW, deleting the T-Engine folder from ~/Library/Application Support doesn't appear to have an effect on launching 1.4.9, and no new folder is created when the 1.4.9 app is launched.
Does anybody have any suggestions, either for further diagnostic information to post or work arounds to try?
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Fri Oct 28, 2016 7:28 am
by darkgod
Damn .. hum is it on staem or not ? if on team can you try the non steam version please ?
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Fri Oct 28, 2016 12:02 pm
by effable
Sorry, I am using the non-Steam version when I experience the bug.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Fri Oct 28, 2016 3:55 pm
by RARaines
I'm not using Steam either. My account predates the placement of TE4 on Steam and I'm not inclined to add another step in between myself and my fix.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Tue Nov 08, 2016 10:43 pm
by binomine
Same error here.
I think the same line :
> Available video driver: dummy
Is OSX using the dummy video driver? I also noticed the DoomRL is also launching with a black screen. It worked in the previous version of OSX.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Wed Nov 16, 2016 3:34 am
by draeath
Case sensitive filesystem? I ran into a similar issue, and in my case it's because the 'CFBundleExecutable' key is 'T-Engine' yet the executable is 't-engine'. If I tried to run t-engine directly, instead of launching the app bundle, I'd get a black screen and the same console message.
Incidentally, this is a bug report on it's own, I'll make a separate report... done,
see here for my workarounds and almost-solution.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Wed Nov 16, 2016 1:43 pm
by darkgod
The case problem is now fixed, simply redownload.
As for the resolution stuff, I'll see if there is an update to sdl to handle that; but sadly this is mostly out of my reach (and please thank apple for trying as hard as they can to make cross platform developers suffer as much as possible..)
Also, 10.5.5 ? isnt that a very old version ? I'm compiling on 10.6 which is alreayd very old and someday I already know I'll have to bump that to 10.9 (which is still rather old)
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Wed Nov 16, 2016 3:45 pm
by effable
The case problem is now fixed, simply redownload.
Um...It's still not working for me.
Using the current version 1.4.9 download (app compiled on October 28, 2016 at 12:12 PM) under OS X 10.12.1, I get still get an empty black window and hang upon launch.
It doesn't create a te4_log.txt file, but this is what it shows in the system.log:
Code: Select all
Nov 16 07:03:10 myComputer com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Nov 16 07:03:10 myComputer logd[66]: _handle_cache_delete_with_urgency(0x7f91cdd1b7c0, 3, 0)
Nov 16 07:03:10 myComputer t-engine[23125]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
Nov 16 07:03:15 myComputer logd[66]: _handle_cache_delete_with_urgency(0x7f91cdea2ae0, 3, 0)
Nov 16 07:03:15 myComputer logd[66]: _handle_cache_delete_with_urgency(0x7f91cdd5c250, 3, 0)
Nov 16 07:03:17 myComputer com.apple.xpc.launchd[1] (com.apple.quicklook[23133]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Nov 16 07:03:17 myComputer com.apple.xpc.launchd[1] (com.apple.quicklook[23132]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Nov 16 07:03:24 myComputer com.apple.xpc.launchd[1] (org.te4.T-Engine.4680[23125]): Service exited with abnormal code: 255
You mentioned that you are building to target OS X 10.6. I assume that there are APIs that you trying to retain and/or avoid by staying with the legacy frameworks, if only to maintain compatibility with a broader range of older user systems -- and to avoid the hassle of rewriting them to use the modern APIs. Regardless, given that version 1.4.8 still runs normally on my system, it wouldn't seem to be a matter of the older frameworks themselves being incompatible with the modern OS.
Let me know if there is any additional diagnostic information I can provide. I'm also happy to run whatever tests that you might need performed to see how things work on the current version of the OS.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Wed Nov 16, 2016 8:46 pm
by darkgod
Wut? You mean 148 works and 149 doesnt ? but but .. hum .. ok
Lets remove the usual suspect first, move away Contents/MacOS/libte4-web.dylib please
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Wed Nov 16, 2016 10:24 pm
by effable
darkgod wrote:Wut? You mean 148 works and 149 doesnt ? but but .. hum .. ok
Yes, it's strange but true. 1.4.8 has worked since it came out on each successive version of OS X, but 1.4.9 fails under 10.12.1.
Lets remove the usual suspect first, move away Contents/MacOS/libte4-web.dylib please
This gets a little more interesting.
The short version is that removing the dylib doesn't really change anything.
The long version is one that I stumbled onto by accident, but is likely highly relevant.
With or without the dylib in place, double clicking on the app icon produces the empty black window described earlier.
With or without the dylib in place, double clicking on the /Contents/MacOS/t-engine executable DOES work, launching the app normally and apparently successfully. There's still some chatter on stdout and the system.log, but the program appears to run fine.
The issue would therefore seem to be something in the assembly of the final app bundle, rather than the code itself.
Does any of that help?
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Thu Nov 17, 2016 8:54 am
by darkgod
Strange, can you check Info.plist if it lists the executable name as "t-engine" and not "T-Engine" ?
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Thu Nov 17, 2016 10:57 am
by binomine
For me at least, 1.4.8 doesn't work.
Re: Bug Report - OSX version 10.5.5 - Can't launch game
Posted: Thu Nov 17, 2016 1:17 pm
by effable
darkgod wrote:Strange, can you check Info.plist if it lists the executable name as "t-engine" and not "T-Engine" ?
It lists CFBundleExecutable as "t-engine" while both CFBundleIdentifier and CFBundleName say "T-Engine" -- as far as I know all three are correct. Certainly the executable itself is "t-engine" while the bundled app is "T-Engine"
I guess there is a workaround (i.e., directly launching the executable inside the app bundle), but it seems as though this really ought to be a trivial fix once we figure out where things went awry. I'm still game to keep trying to troubleshoot if you have any more ideas.
Thanks.