This report sounds like feature request. I think you would have best chance if you can make PR for this issue.
Will close, since this tracker is only for bugs and errors. For more information…
I wasn't able to reproduce crash with 3.6 or 4.4 version. Does this issue happen with 4.4 build? Can you attach crash report here?
Thanks for the report, but please use other channels for user feedback and feature requests: https://developer.blender.org/docs/handbook/communication/user_feedback/ For more information on why…
Can't reproduce on Linux with RX 550 GPU. Can you run Blender from terminal and check if there are any crash logs?
Or Actually I can close as duplicate of #127634, since technically the issue is the same, and workaround as well...
Isn't the stack of inputs and effects in the timeline basically a different view of a compositor node tree? If so, maybe it's possible to convert the task of rendering a frame in the VSE to an…
That also is not quite correct. CPU is needed to do things. In this case mostly to compile shaders.
Can not reproduce this on current machine, but I am pretty sure, this happened to me before. In any case, I am not sure if I would say, that this is a bug, but it is at least not nice behavior.
If not using steam, then please try running from terminal and check for blender.crash.txt file created in /tmp.
Could be limitation, so won't assign high prio. @glukoz can you check?
You are misunderstanding how this works. Material preview is implemented in GPU only. Rendering device selector in preferences is for Cycles engine only. Even still this report would be then about…
