Fix for RAM usage & WebGL Context Lost on Windows Devices with Some Integrated Intel GPUs

[sedghi]

Seems like there is a bug in Chrome for Windows users with some models of the integrated Intel GPUs. As a result, OHIF and/or Cornerstone3D demos may experience rendering issues, with the GPU process consuming an excessive amount of memory for volume viewports. As a result, the webGL context may be lost and the browser crashes.

The bug has been narrowed down to be inside the Chrome and not from us, more especifically the Angle backend component of Chromium. While we are working on reporting this bug, we have a solution that has proven to be effective in fixing this issue which has worked on 4 separate machines having the same issue.

1. Ensure that your GPU is not blacklisted by your browser. To enable ignore-blacklist, go to chrome://flags/#ignore-gpu-blocklist and enable it. We have one machine who had NVIDIA GeForce RTX 2060 and it was blacklisted.
2. Next, make sure that your browser is configured to use one of the following:
   • Angle with the latest available WebGL backend (options are: d3d11on12, vulkan)
   • Angle with OpenGL

For Chrome users, you can change your angle value by going to chrome://flags/#use-angle and changing the value as described.

(Note that your selected Angle must be supported by your graphics card and driver. While Chrome and Firefox will always display available options, it's important to check that your selected Angle is compatible with your machine.)

🎸 Special thanks to Rodolfo (@ladeirarodolfo )for finding this solution and sharing it with the community! 🎸 🎸 Special thanks to the QIPCM team who helped us thoroughly debug this on various Windows machines. 🎸

PS:

• d3d11 is different than d3d11on12, use d3d11on12 if you have it
• For edge browser, you can set the same flag using edge://flags/#use-angle
• For Mac users, we recommend using Default Angle settings.
• Firefox users, please navigate to https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers and refer to the section "How to force enable...." to enable ignore-blacklist.

[ranasrule]

no luck here....same error no matter which ANGLE I use

[salimkanoun]

Hi there I have a device with this problem, In chome and edge turning the angle on D11OnD12 solved the problem,

But in firefox no luck I tried to pass true webgl.force-enable webgl.msaa-force layers.acceleration.force-enabled

also try webgl.angle.force-d3ond11

Non of these settings solves this problem on latest firefox, any idea of any settings should i play with ? Or should we just say to users to avoid firefox ?

[ashinnotfound]

no luck here....same error no matter which ANGLE I use

same with u, have u ever solved it

[sedghi]

you are using a very old OHIF based on UI, you can try using the latest

[rathwale]

@sedghi - did we get a chance to report this bug to Chromium community? do we have any reference/bug link? want to understand the impact on customers who will be facing this.

[sedghi]

No i have not

[David2k13]

Or turn off the GPU acceleration function