Cheered too soon - there are random but often crashes (gtk3). Can I send the crash log somehow?
Hallo Besucher, der Thread wurde 14k mal aufgerufen und enthält 115 Antworten
letzter Beitrag von Retro Haudegen am
Vice am Mac - Versionen, Tastaturlayout
- phat-phu
- Erledigt
-
-
Melbourne!
Cheered too soon - there are random but often crashes (gtk3). Can I send the crash log somehow?
Ah, that's a shame It's been rock solid on my main development machine. Do the crashes happen in response to UI things like clicking on menus etc or when you are otherwise doing nothing while the emulator runs?
-
No, not when clicking. It just crashes randomly. Last time I tried to configure the joystick, another time while running a game. But I have a crash log if you want.
-
No, not when clicking. It just crashes randomly. Last time I tried to configure the joystick, another time while running a game. But I have a crash log if you want.
Yes please - if you could attach it the VICE bug tracker i'll take a look. The project isn't necessarily built in a way that will allow me to reconstruct what happened from the log but it might give me a clues. I've just been playing with a 2010 MBP (Core 2 Duo) running 10.9.5 and it seems ok so far. What CPU do you have, and what CPU % does Activity Monitor say that x64sc is using?
-
It's easier to add the crash log here.
I have an 3.5 GHz i7 late 2013 iMac. Activity monitor displays about 38 % activity.
It just crashes again - I only started x64sc, smart attached at d64 image and loaded a game from it with the regular load command - after a while loading it simply crashes.
-
It's easier to add the crash log here.
I have an 3.5 GHz i7 late 2013 iMac. Activity monitor displays about 38 % activity.
It just crashes again - I only started x64sc, smart attached at d64 image and loaded a game from it with the regular load command - after a while loading it simply crashes.
Hm, very odd, and lots of useful info in that log, thanks. Can you try running with default settings via -default on the command line? I've notice that enabling mouse grab crashes on 10.9 which i'll fix. Anything we can figure out how to replicate I should be able to fix.
-
Thanx! I'll try it later and report later, not home at the moment...
-
OK, just tried. Still crashes. New crash log enclosed.
./x64sc -default
2020-08-30 18:33:15.071 x64sc[55912:507] Invalid color System, labelColor (warning given only once)
/Applications/Emulators/VICE 3.4/x64sc.app/Contents/Resources/script: line 39: [: /Applications/Emulators/VICE: binary operator expected
-
Now the crash happened even some seconds after starting the app. Without clicking anything.
-
OK, just tried. Still crashes. New crash log enclosed.
./x64sc -default
2020-08-30 18:33:15.071 x64sc[55912:507] Invalid color System, labelColor (warning given only once)
/Applications/Emulators/VICE 3.4/x64sc.app/Contents/Resources/script: line 39: [: /Applications/Emulators/VICE: binary operator expected
So that non-fatal script error is the result of some missing quotes in the 'script' file, which only manifest as a problem if there is a space in the path somewhere (VICE 3.4). I've fixed that. By the way, the scripts in the bin folder in the root of the VICE folder is a more convenient way to invoke VICE via command line.
I've also fixed the crash on mouse grab - I was using some functionality that was added in OSX 10.10. But I can't replicate any other kind of crash I wonder if it's specific to your GPU somehow. My 10.9.5 machine has an older NVidia GPU than yours (320M, 256MB) and it works reliably.
In both crash logs I see the same sequence. Some sort of internal GDK (GTK) problem where it seems to reach a line of code that it shouldn't. I think there's a good chance that a crash message would be logged to the OS X Console.app - would you mind testing if that is the case? Just open Console.app, make sure your iMac is selected at the top left, put x64sc in the search and then run x64sc and wait for it to crash.
-
Downloaded the latest version, run it - and crashed several seconds later. This was in the console:
31.08.20 15:09:28,173 x64sc[56900]: Invalid color System, labelColor (warning given only once)
31.08.20 15:09:44,306 x64sc[56922]: GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/Current/AppKit,_NSCreateAppKitServicesMenu) failed.
31.08.20 15:09:47,337 ReportCrash[56925]: Saved crash report for x64sc[56922] version 0 to /Users/cws/Library/Logs/DiagnosticReports/x64sc_2020-08-31-150947_Clarks-iMac-2.crash
Enclosed the crash log.
-
Does it run completely independent or is it possible that already installed older file versions interfere in some way? Installed homebrew and MacPorts, several other libraries over time that other projects needed, updated GTK some time ago,etc.
-
It should run completely independently, although i've noticed that it loads some locale related things from /opt/local if they are there. Based on your crash log I don't see any evidence of local GTK etc libs being pulled in.
Could you run the following command in a terminal, then launch x64sc, and share the output?
-
By the way, I get those same warnings/errors on my OS X 10.9 machine but without any crashes 3 seconds later. Given that you seem to have some dev happening on your machine, is there any chance you could try building and running it in Xcode to see if any more interesting information is revealed? CMake / Xcode build instructions
-
I'll do that command line later. And no, no development here, only some things I installed over time as needed for some programs I installed. And sorry, no idea of any dev, no idea at all.
-
With the terminal command I get this line:
dtrace: description 'syscall::*open*:entry ' matched 9 probes
And the logs enclosed.
-
Anything new?
-
Thanks for the log .. there's no evidence of your version opening a local file in a different way to on my machines. I looked at it at the time but hadn't replied.
So i'm pretty confused at this point. Is there any chance we could work through the process of you building it yourself on the machine - it's pretty a pretty easy process? I'd like to know if it starts working if it is built locally - if so, this means that my build environment is not yet fully compatible with 10.9.5. I might need to move to making official release builds on my 10.9.5 machine.
-
What is needed to build? I do not think I have Xcode installed.
-
VICE macOS build instructions are here. You could try without installing Xcode itself, I have vague memories of the xcode-select --install command being able to install the command line build tools without the whole Xcode install being needed. Otherwise you can install Xcode 6.2 which is the most recent version that will run on OS X 10.9.