Eevee-Next Intel Arc: Switching to Eevee-next causes Blender to stop redrawing #115942

New Issue

Vik · 2023-12-08T14:45:33+01:00

Vik commented

2023-12-08 14:45:33 +01:00

System Information
Operating system: Windows 11
Graphics card: Intel Arc A770 16GB, driver 4972. There might be a new driver in a few hours.
blender_system_info.txt

Blender Version
Broken: version: 4.1.0 Alpha, commit date: 2023-12-08 00:25, hash: 2b0448c91d7a
Worked: version: 4.1.0 Alpha, commit date: 2023-10-08 17:52, hash: a3831fe7af80

Short description of error

Intel has their own issue tracker where they take issues, example other open Eevee-next issue: https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/559. At the same time, I've seen a past issue similar to this fixed on Blender's side #113447. Where should I report? Both?

Switching to rendered shading with Eevee-next selected causes Windows to freeze for a bit. It then unfreezes, and it looks like Blender's UI stops redrawing but Blender isn't frozen. Borders between areas change the cursor to resize them, resizing them properly makes the cursor change elsewhere from before, and playing an animation with sound by clicking the play button correctly makes sound.

Video, with throbber (to indicate the freeze) and sound included:

A more severe version of the issue mentioned at IGCIT is visible in the video, when not crashing.

Exact steps for others to reproduce the error

Open the attached eeveenexttest.blend file
Fullscreen Blender on a 1080p monitor
Switch to rendered preview

The issue occur (sometimes).
Shrinking the area of the screen the viewport takes up will not cause this issue.
Tested on a 1080p screen with Blender maximized.
If not maximized, you may need to increase the viewport's area.
Resizing a small viewport that's already in rendered shading to be bigger does not freeze.

Uneventful debug output: blender_debug_output.txt
SSU: igcit_ssu_4972.txt

**System Information** Operating system: Windows 11 Graphics card: Intel Arc A770 16GB, driver 4972. There might be a new driver in a few hours. [blender_system_info.txt](/attachments/c9f8d08c-0a4a-442a-9f40-626ea5f46f15) **Blender Version** Broken: version: 4.1.0 Alpha, commit date: 2023-12-08 00:25, hash: `2b0448c91d7a` Worked: version: 4.1.0 Alpha, commit date: 2023-10-08 17:52, hash: `a3831fe7af80` **Short description of error** Intel has their own issue tracker where they take issues, example other open Eevee-next issue: https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/559. At the same time, I've seen a past issue similar to this fixed on Blender's side https://projects.blender.org/blender/blender/pulls/113447. Where should I report? Both? Switching to rendered shading with Eevee-next selected causes Windows to freeze for a bit. It then unfreezes, and it looks like Blender's UI stops redrawing but Blender isn't frozen. Borders between areas change the cursor to resize them, resizing them properly makes the cursor change elsewhere from before, and playing an animation with sound by clicking the play button correctly makes sound. Video, with throbber (to indicate the freeze) and sound included: <video src="/attachments/2c001ff4-09b9-4d03-8230-019bb47e5d52" title="2023-12-08_15-39-19.mkv" controls></video> A more severe version of the issue mentioned at IGCIT is visible in the video, when not crashing. **Exact steps for others to reproduce the error** - Open the attached [eeveenexttest.blend](/attachments/65f57c07-f2e2-4c96-ba9a-82594b06be77) file - Fullscreen Blender on a 1080p monitor - Switch to rendered preview The issue occur (*sometimes*). Shrinking the area of the screen the viewport takes up will not cause this issue. Tested on a 1080p screen with Blender maximized. If not maximized, you may need to increase the viewport's area. Resizing a small viewport that's already in rendered shading to be bigger does not freeze. Uneventful debug output: [blender_debug_output.txt](/attachments/9c544443-8113-4761-ac90-71ddc6440981) SSU: [igcit_ssu_4972.txt](/attachments/2fa542cd-6629-4460-8f4d-168336760dfc)

igcit_ssu_4972.txt

35 KiB

blender_system_info.txt

17 KiB

blender_debug_output.txt

10 KiB

eeveenexttest.blend

157 KiB

2023-12-08_15-39-19.mkv

9.6 MiB

Vik added the

labels 2023-12-08 14:45:33 +01:00

Germano Cavalcante commented

2023-12-08 19:16:28 +01:00

Hi,

I've updated the description, and upon review, I noticed that the steps I extracted differ from the ones shown in the video.
This difference was intentional in the original description?

If confirmed, this report will be forwarded to the appropriate team for further investigation.

Hi, I've updated the description, and upon review, I noticed that the steps I extracted differ from the ones shown in the video. This difference was intentional in the original description? If confirmed, this report will be forwarded to the appropriate team for further investigation.

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-12-08 19:16:37 +01:00

Vik commented

2023-12-08 19:27:26 +01:00

Hi,

I've updated the description, and upon review, I noticed that the steps I extracted differ from the ones shown in the video.
This difference was intentional in the original description?

If confirmed, this report will be forwarded to the appropriate team for further investigation.

The video is a bit different to show the issue more clearly. You don't need to have a throbber on the side, a 2nd Blender instance, or make the viewport smaller first, or have a speaker, this is moreso to demonstrate the additional quirks of the issue.

You do need to keep the lamps. Removing them causes the issue to happen much less often.

To make it simplest, just

Get and open the blend
Maximize Blender on a 1080p monitor
Switch to rendered preview
Issue

Here's another video without anything extra. To me, it seems a bit hard to tell what exactly happened.

> Hi, > > I've updated the description, and upon review, I noticed that the steps I extracted differ from the ones shown in the video. > This difference was intentional in the original description? > > If confirmed, this report will be forwarded to the appropriate team for further investigation. The video is a bit different to show the issue more clearly. You don't need to have a throbber on the side, a 2nd Blender instance, or make the viewport smaller first, or have a speaker, this is moreso to demonstrate the additional quirks of the issue. You do need to keep the lamps. Removing them causes the issue to happen much less often. To make it simplest, just - Get and open the blend - Maximize Blender on a 1080p monitor - Switch to rendered preview - Issue Here's another video without anything extra. To me, it seems a bit hard to tell what exactly happened. <video src="attachments/a9c2ddf7-63d6-40be-8e69-f30843513122" title="2023-12-08_15-39-19.mkv" controls></video>

2023-12-08_20-34-33.mkv

1.4 MiB

Germano Cavalcante added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-12-08 19:31:52 +01:00

Germano Cavalcante commented

2023-12-08 19:37:59 +01:00

This appears to be a duplicate of:
#114597: EEVEE Next: Blender freezing when render mode is selected

And possibly related to:
#115718: Blender 4.1 Alpha's "EEVEE Next" lagging to the point of unusability, and crashing
#113618: Abnormal Behaviour in EEVEE Next with Intel Xe Graphics
#115396: Blender 4.0 crashes on Intel Arc A770

#114597 is already being handled by the developers. So I will merge reports.
Please subscribe in #114597 if you want to see further updates

This appears to be a duplicate of: #114597: EEVEE Next: Blender freezing when render mode is selected And possibly related to: #115718: Blender 4.1 Alpha's "EEVEE Next" lagging to the point of unusability, and crashing #113618: Abnormal Behaviour in EEVEE Next with Intel Xe Graphics #115396: Blender 4.0 crashes on Intel Arc A770 #114597 is already being handled by the developers. So I will merge reports. Please subscribe in #114597 if you want to see further updates

Germano Cavalcante closed this issue

2023-12-08 19:38:05 +01:00

Blender Bot added

and removed

labels 2023-12-08 19:38:07 +01:00

Germano Cavalcante referenced this issue

2023-12-08 19:43:04 +01:00

EEVEE Next: Blender freezing when render mode is selected #114597

Jeroen Bakker added

and removed

labels 2023-12-21 09:37:33 +01:00

Jeroen Bakker added this to the 4.1 milestone 2023-12-21 09:37:37 +01:00

Jeroen Bakker reopened this issue

2023-12-21 09:37:42 +01:00

Jeroen Bakker added this to the EEVEE & Viewport project 2023-12-21 09:38:00 +01:00

Jesse Yurkovich added the

Module

EEVEE & Viewport

label 2023-12-28 11:24:35 +01:00

Jeroen Bakker modified the milestone from 4.1 to 4.2 LTS

2024-03-13 16:24:05 +01:00

Jeroen Bakker commented

2024-03-13 16:25:36 +01:00

@Viktor_smg is this still the case?

Vik commented

2024-03-13 19:34:37 +01:00

@Viktor_smg is this still the case?

I can still reproduce this with 4.2 443ea628c5 and driver 5333.
Windows does not freeze for a bit anymore, but Blender still stops redrawing and still responds to inputs like shown with audio.

> @Viktor_smg is this still the case? I can still reproduce this with 4.2 443ea628c5c8 and driver 5333. Windows does not freeze for a bit anymore, but Blender still stops redrawing and still responds to inputs like shown with audio.

Philipp Oeser added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee-Next Intel Arc: Switching to Eevee-next causes Blender to stop redrawing #115942