Graphs sometimes fail to load. May be hardware; may be code?

What I’m trying to do

I sometimes like to have the main graph open to one side of my workspace and the local graph open in a small sidebar window. Often a graph will fail to load, or disappear while I’m working. When this happens a console error is generated:

[.WebGL-0000534803294E00]GL Driver 
Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): 
GPU stall due to ReadPixels 
(this message will no longer repeat)

Things I have tried

Didn’t find anything relevant in the forum. Usually quitting the window, opening another and reloading the graph works.


Windows 11 Professional (x64) Version 22H2
Memory: 16Gb
Processor: 3.70 gigahertz Intel Core i7-8700K
Board: ASRock Z390 Phantom Gaming-ITX/ac
Video support: “Intel® UHD Graphics Built-in Visuals : Intel® Quick Sync Video with AVC, MVC (S3D) and MPEG-2 Full HW Encode1, Intel® InTru™ 3D, Intel® Clear Video HD Technology, Intel® Insider™, Intel® UHD Graphics, DirectX 12”


I’m not a gamer and not very knowledgeable about GPU specs and issues, but this Phantom Gaming-ITX mobo is supposed to have decent onboard graphics processing.

I did find an interesting reference to “ReadPixels” on StackOverflow, where a commenter offered:

readPixels is fundamentally a blocking, pipeline-stalling operation, and it is always going to kill your performance wherever it happens, because it’s sending a request for data to the GPU and then waiting for it to respond, which normal draw calls don’t have to do.

Do readPixels as few times as you can (use a single combined buffer to read from). Do it as late as you can. Everything else hardly matters.

Can anyone here suggest whether I have a personal hardware limitation, or if this is an unusual coding issue that should maybe be addressed as a bug?

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.