-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS problems #118
Comments
Thanks for the report. I am not sure why you'd have issues in fullscreen considering I request a borderless window instead of exclusive mode - but maybe that works differently in MacOS. The grey color is drawn by using the GPU's "clear color" - in fullscreen maybe there's an assumption that the entire screen will be drawn so this is turned off? If you toggle between scaling modes in fullscreen, are any artifacts of the previous display size left behind? The reboot issue is very concerning. Obviously I don't want to damamge anyone's computer! In theory nothing a program could possibly do should be able to cause the operating system to unintentionally reboot, but there are always new bugs to find. Are you running MartyPC as a normal user or an administrator? The colors + rebooting makes me concerned a bit about potential GPU issues. Does your system get very hot? Do you have a way to monitor GPU/CPU temperatures? Do you have a video game or other 3d application you can test to make sure that using the GPU itself isn't an issue? Could you open Activity Monitor while MartyPC is running and examine the values for CPU % , GPU % and memory usage? Does memory usage continue to climb while MartyPC is running? |
Can you try building the egui example from here: and see if you have any of the same issues? Can you go back to the 0.1.3 release and see if it does the same? |
Yes, stripes are there, just red:
Yes, it does the same. |
If you run the Pixels example for 30+ minutes does it also reboot your system? |
No, it does not. I ran Pixels all day without issues. The only abnormalities were the CPU load: ~30% when Pixels is in focus and ~120% when minimized to the tray. I'll report this on their GitHub. Regarding macOS instability, it seems to occur when debug features (CPU state, instruction history, disassembly, etc.) are activated. I'll try playing a DOS game for an hour without these features enabled. |
can you show me the Performance window in MartyPC? also, can you see if you have stripes in the wgpu examples (upstream of pixels) |
If the issue is upstream of Pixels i'd say it is more appropriate to open it on wgpu. Pixels maintainer can't fix it |
Hi @dbalsom, |
I suppose I can add a macos_stripe_fix flag to the config and then when we resize for fullscreen subtract one from the resize dimensions. |
That would be awesome. |
While testing the fix for #120, I encountered the freeze and reboot again. I've sent another report to Apple :) |
I bumped the wgpu version in the current branch. Can you check if you still have the same problems? if you're still seeing the stripes, try the |
This workaround works!!! Thank you. |
Hi @dbalsom, Do you know what MartyPC is doing when emulation is paused? One CPU core is constantly at 100% utilization. |
that's odd. it shouldn't really do anything different, but obviously it will spend less time per frame emulating, but it should just do updates and yield. can you show me the performance window when paused? |
Describe the bug
I have two issues on macOS:
Environment (please complete the following information):
Build info
The text was updated successfully, but these errors were encountered: