Skip to content
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

Advanced OpenGL apps may cause graphical glitches and/or GPU hangs #158

Open
VisualEhrmanntraut opened this issue Sep 6, 2023 · 79 comments
Assignees
Labels
Bug Something isn't working
Milestone

Comments

@VisualEhrmanntraut
Copy link
Member

VisualEhrmanntraut commented Sep 6, 2023

Advanced OpenGL software, like Chrome, may have artefacts or freeze the system.

To Reproduce

  1. Open OpenGL software like Chrome
  2. Observe

Expected behavior
The software working perfectly fine.

Screenshots
Screenshot 2023-09-06 at 10 45 40

System Information:
N/A; Happens on all ASIC types and macOS versions.

Additional context
Metal software all work fine. It is likely a bug in the OpenGL library.

@VisualEhrmanntraut VisualEhrmanntraut added the Bug Something isn't working label Sep 6, 2023
@VisualEhrmanntraut VisualEhrmanntraut added this to the Version 1.0.0 milestone Sep 6, 2023
@VisualEhrmanntraut VisualEhrmanntraut self-assigned this Sep 6, 2023
@VisualEhrmanntraut VisualEhrmanntraut pinned this issue Sep 6, 2023
@Xtuber14

This comment has been minimized.

@VisualEhrmanntraut
Copy link
Member Author

ANGLE is for WebGL. Nothing to do with Chrome itself glitching out.

@b00t0x

This comment has been minimized.

@DepsCian

This comment has been minimized.

@Xtuber14

This comment has been minimized.

@jalavoui

This comment has been minimized.

@Xtuber14

This comment has been minimized.

@jalavoui

This comment has been minimized.

@b00t0x

This comment has been minimized.

@shenfu1991

This comment has been minimized.

@VisualEhrmanntraut

This comment has been minimized.

@jalavoui

This comment has been minimized.

@VisualEhrmanntraut
Copy link
Member Author

Talking about that workaround... I just realised something:
With the VTable wrap hack the team ex-member came up with, if the called function inside the wrap calls another virtual function in the this pointer, then the wrong function gets called

@jalavoui

This comment was marked as spam.

@VisualEhrmanntraut
Copy link
Member Author

(The VTable hack has to do with HWAlignManager used inside it for calculations)

@alvindimas05

This comment has been minimized.

@truongvantuan

This comment has been minimized.

@alvindimas05

This comment has been minimized.

@revogabe
Copy link

@VisualEhrmanntraut Do you have any predictions if we can have any solution for chrome-based browsers natively in the future?

@VisualEhrmanntraut
Copy link
Member Author

New prediction available: No prediction available.

@alvindimas05

This comment was marked as off-topic.

@txrm
Copy link

txrm commented Oct 4, 2023

DOSBOX's OpenGL freezes the system immediately, looking into what triggers it since it's a fast and reliable crash.

Config field is output = surface | overlay | opengl | openglnb | ddraw

@VisualEhrmanntraut
Copy link
Member Author

VisualEhrmanntraut commented Nov 11, 2023

Chrome seems to die due to a command sent by libGLES2. Relevant log attached. (This is an Electron app, therefore uses Chromium)
YouTube_Music_Helper_GPU_2023-10-28-113038_MacBook-Pro.crash.txt

@VisualEhrmanntraut
Copy link
Member Author

VisualEhrmanntraut commented Nov 11, 2023

Also I found that in AMDRadeonX5000GLDriver, function _gfx9_HwInfoInitData and _amdUbm_HWL_Init, that the device family is hardcoded instead of being read from the accelerator.

@bfitzgit23

This comment has been minimized.

@bfitzgit23

This comment has been minimized.

@VisualEhrmanntraut
Copy link
Member Author

#158 (comment)

@ChefKissInc ChefKissInc locked and limited conversation to collaborators Feb 7, 2024
@VisualEhrmanntraut VisualEhrmanntraut changed the title Advanced OpenGL apps may have artefacts or freeze the system Advanced OpenGL apps may cause graphical glitches and/or GPU hangs Mar 14, 2024
@VisualEhrmanntraut
Copy link
Member Author

VisualEhrmanntraut commented Mar 25, 2024

The situation has been improved with the latest commits. For instance, Firefox now works, and things like Chrome don't instantly kill the system anymore for some that it did. Verified by my internal quality control group.

Here's a few screenshots:

IMAGE 2024-03-25 12:51:10
IMAGE 2024-03-25 12:51:19
IMAGE 2024-03-25 12:51:49

Note that there's also some other misc changes in the build they're using, but I think those aren't related.

@szmarczak

This comment was marked as off-topic.

@VisualEhrmanntraut
Copy link
Member Author

You ran something, it corrupted the VRAM, and now stuff looks like this.

@Memelord187
Copy link

So the latest artifact that I'm fetching from GitHub has those recent changes in it? I still have glitches on chromium based apps with it, but I'm not really sure if that version already includes those changes

@VisualEhrmanntraut
Copy link
Member Author

Never said anything about glitches being fixed.

@Memelord187
Copy link

he situation has been improved with the latest commits. For instance, Firefox now works, and for some people that things like Chrome instantly killed the system doesn't happen anymore. Verified by my internal quality control group.

I thought this meant apps shouldn't glitch out the entire screen; the OS isn't crashing, but the entire screen gets broken once I launch Chrome-based apps

@VisualEhrmanntraut
Copy link
Member Author

That would mean the issue is fixed, so the issue would not be open anymore. The things I listed is what seemed to be fixed in the testing. There were also reports of other issues be fixed after the changes were added, like black screens and other instabilities.

@jpsaturnino
Copy link

jpsaturnino commented Apr 6, 2024

Also I was having problem with nextflix/crunchroll/amazon on safari based browsers where the media even started (gives black screen or a page error), but now in firefox works perfectly and not problems so far.

I think this may be related to DRM compatibility, apparently, with the last updates the OpenGL is using better the DRM infrastructure

Thanks for the update!

I'm using Sonoma 14.3.1 (23D60) on a R7 5700G with iGPU 2GB VRAM dedicated

@VisualEhrmanntraut
Copy link
Member Author

Safari uses hardware DRM, which isn't implemented here. Firefox uses software DRM.

@phpete1

This comment was marked as off-topic.

@b2nzy
Copy link

b2nzy commented May 5, 2024

Hi NootedRed team

Thanks for all your hardwork on the kext!

I'm fairly new to hackintosh, and I'm experiencing this same issue.

I'm running Ventura. Would reverting to BigSur work?

nope

@AlbeRCLife
Copy link

Hello!
Thanks for all your effort!

Just to add to this topic in case anyone comes from google with the same issue:

TL; DR: I had 512 VRAM for the iGPU (5700G) and after setting it to at least 3GB I could at least log in without issues to close the apps.

I had Chrome opened with roughly 5 or 6 tabs and vscode with just the init screen. After powering off the system with the "open all apps as they were before" checked if I restarted the system it would do the following:

  • Let me log in with my password
  • The apps tried to open but everything just froze
  • If I waited for a bit without touching anything (but moving the mouse, of course) the log in screen prompting for the password would reappear again and it would keep this loop without me being able to close any app or do anything really

Hope this helps someone (and yeah, I know the docs already mentioned that it was better to have 1GB+ for VRAM but I just couldn't find it in the BIOS until I searched for a freaking video as it was kind of obfuscated within the BIOS)

@yogesh-aggarwal
Copy link

yogesh-aggarwal commented May 24, 2024

Hello!
Thanks for all your effort!

Just to add to this topic in case anyone comes from google with the same issue:

TL; DR: I had 512 VRAM for the iGPU (5700G) and after setting it to at least 3GB I could at least log in without issues to close the apps.

I had Chrome opened with roughly 5 or 6 tabs and vscode with just the init screen. After powering off the system with the "open all apps as they were before" checked if I restarted the system it would do the following:

  • Let me log in with my password
  • The apps tried to open but everything just froze
  • If I waited for a bit without touching anything (but moving the mouse, of course) the log in screen prompting for the password would reappear again and it would keep this loop without me being able to close any app or do anything really

Hope this helps someone (and yeah, I know the docs already mentioned that it was better to have 1GB+ for VRAM but I just couldn't find it in the BIOS until I searched for a freaking video as it was kind of obfuscated within the BIOS)

Just create a pendrive with WhateverGreen (make sure NootedRed is either disabled or removed completely) and disable "Use graphics acceleration when available" in Settings > System of chrome.

I know this will offload all the work from GPU to CPU but you'll be able to browse at least.

After that you can just simply boot from your Mac's EFI.

Nonetheless, we need a solution for this as if I talk about my R3 2200G with only iGPU in place, it snatches a lot of performance that could possibly have been spent elsewhere usefully.

@VisualEhrmanntraut
Copy link
Member Author

ugh, how many times will I have to say that WhateverGreen is useless if you don't have a native macOS GPU...

@JakoDel
Copy link

JakoDel commented May 24, 2024

Hello!
Thanks for all your effort!
Just to add to this topic in case anyone comes from google with the same issue:
TL; DR: I had 512 VRAM for the iGPU (5700G) and after setting it to at least 3GB I could at least log in without issues to close the apps.
I had Chrome opened with roughly 5 or 6 tabs and vscode with just the init screen. After powering off the system with the "open all apps as they were before" checked if I restarted the system it would do the following:

  • Let me log in with my password
  • The apps tried to open but everything just froze
  • If I waited for a bit without touching anything (but moving the mouse, of course) the log in screen prompting for the password would reappear again and it would keep this loop without me being able to close any app or do anything really

Hope this helps someone (and yeah, I know the docs already mentioned that it was better to have 1GB+ for VRAM but I just couldn't find it in the BIOS until I searched for a freaking video as it was kind of obfuscated within the BIOS)

Just create a pendrive with WhateverGreen (make sure NootedRed is either disabled or removed completely) and disable "Use graphics acceleration when available" in Settings > System of chrome.

I know this will offload all the work from GPU to CPU but you'll be able to browse at least.

After that you can just simply boot from your Mac's EFI.

Nonetheless, we need a solution for this as if I talk about my R3 2200G with only iGPU in place, it snatches a lot of performance that could possibly have been spent elsewhere usefully.

the UN should make "modern macOS must be run with 3D accel working" an international law.
btw, what's the point of ruining your entire system just to run chrome? use win/linux at that point. safari and firefox are, a few minor incompatibilities aside, just as good and you'd be helping in the "fight" against chromium becoming the only platform.

@VisualEhrmanntraut
Copy link
Member Author

at least use Firefox... so much better than Google's crap and also works pretty much flawlessly with the latest NootedRed

@JakoDel
Copy link

JakoDel commented May 24, 2024

at least use Firefox... so much better than Google's crap and also works pretty much flawlessly with the latest NootedRed

yep you beat me to it lol. edited at the same time you posted. and I agree wholeheartedly.

@Wangxxis
Copy link

Wangxxis commented Jun 3, 2024

at least use Firefox... so much better than Google's crap and also works pretty much flawlessly with the latest NootedRed

GPU hangs in open a gitlab repository in firefox...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Status: 📋 Backlog
Development

No branches or pull requests