ERROR ACCESS VIOLATION when switching to evee rendered view #79737

New Issue

System Information
Operating system: Windows 10
Graphics card: NVIDIA 1080 TI
CPU: i7-8700K
RAM: 32GB

Blender Version
Broken: 2.83 LTS, 2.90, 50b435cbaa
Worked: blender-2.82a-windows64

Short description of error
A scene I have works in shows the rendered view just fine, but crashes when switching to rendered view in Evee

Exact steps for others to reproduce the error
Open up the file
switch to evee rendered view and it will crash
I've added the blend file and crash text report blender wrote
cyberpunk landscape.crash.txt cyberpunk landscape.blend

**System Information** Operating system: Windows 10 Graphics card: NVIDIA 1080 TI CPU: i7-8700K RAM: 32GB **Blender Version** Broken: 2.83 LTS, 2.90, 50b435cbaa Worked: blender-2.82a-windows64 **Short description of error** A scene I have works in shows the rendered view just fine, but crashes when switching to rendered view in Evee **Exact steps for others to reproduce the error** Open up the file switch to evee rendered view and it will crash I've added the blend file and crash text report blender wrote [cyberpunk landscape.crash.txt](https://archive.blender.org/developer/F8773862/cyberpunk_landscape.crash.txt) [cyberpunk landscape.blend](https://archive.blender.org/developer/F8773844/cyberpunk_landscape.blend)

Added subscriber: @lysol

Added subscriber: @Jewls

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Can confirm.
There´s definitve something wrong here.
That file has a heavy consume of ram so im not sure its a "out of ram" issue.

Can confirm. There´s definitve something wrong here. That file has a heavy consume of ram so im not sure its a "out of ram" issue.

Added subscriber: @iss

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

File is very complex and it would be best if @lysol could try to simplify it as much as possible by removing objects and checking if bug is still there.

But I can confirm crash, and it does look like a bug

 	vcruntime140.dll!00007ffacecc1480()	Unknown
>	[Inline Frame] blender.exe!eevee_lightprobes_extract_from_cache(EEVEE_LightProbesInfo * pinfo, LightCache *) Line 712	C

 	blender.exe!EEVEE_lightprobes_cache_finish(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata) Line 727	C
 	blender.exe!eevee_cache_finish(void * vedata) Line 166	C
 	[Inline Frame] blender.exe!drw_engines_cache_finish() Line 1037	C
 	blender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1494	C
 	blender.exe!DRW_draw_view(const bContext * C) Line 1404	C
 	[Inline Frame] blender.exe!view3d_draw_view(const bContext *) Line 1598	C
 	blender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1622	C
 	blender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 543	C
 	blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 697	C
 	blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 825	C
 	blender.exe!wm_draw_update(bContext * C) Line 1028	C
 	blender.exe!WM_main(bContext * C) Line 482	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 548	C
 	[External Code]

File is very complex and it would be best if @lysol could try to simplify it as much as possible by removing objects and checking if bug is still there. But I can confirm crash, and it does look like a bug ``` vcruntime140.dll!00007ffacecc1480() Unknown > [Inline Frame] blender.exe!eevee_lightprobes_extract_from_cache(EEVEE_LightProbesInfo * pinfo, LightCache *) Line 712 C blender.exe!EEVEE_lightprobes_cache_finish(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata) Line 727 C blender.exe!eevee_cache_finish(void * vedata) Line 166 C [Inline Frame] blender.exe!drw_engines_cache_finish() Line 1037 C blender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1494 C blender.exe!DRW_draw_view(const bContext * C) Line 1404 C [Inline Frame] blender.exe!view3d_draw_view(const bContext *) Line 1598 C blender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1622 C blender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 543 C blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 697 C blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 825 C blender.exe!wm_draw_update(bContext * C) Line 1028 C blender.exe!WM_main(bContext * C) Line 482 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 548 C [External Code] ```

I've removed every object in the scene, and it still crashes. Now blender is writing out this crash file. @ISS. I've attached the blend file with no objects in it
{F8778101}aria-debug-7116.log

I've removed every object in the scene, and it still crashes. Now blender is writing out this crash file. @ISS. I've attached the blend file with no objects in it {[F8778101](https://archive.blender.org/developer/F8778101/cyberpunk_landscape_no_objects.blend)}[aria-debug-7116.log](https://archive.blender.org/developer/F8778100/aria-debug-7116.log)

I get same stach trace still.

What's more important is, that you removed all data and your .blend file is still 17MB. I am not sure what file aria-debug-7116.log is. Blender shouldn't produce such file.
I will assume this is caused by some addon. I can see some data from node wrangler, but not sure if that would explain such big filesize.

Can you click on Help > Save System Info and upload saved file?

I get same stach trace still. What's more important is, that you removed all data and your .blend file is still 17MB. I am not sure what file `aria-debug-7116.log` is. Blender shouldn't produce such file. I will assume this is caused by some addon. I can see some data from node wrangler, but not sure if that would explain such big filesize. Can you click on Help > Save System Info and upload saved file?

system-info.txt
Here is the system info

[system-info.txt](https://archive.blender.org/developer/F8780447/system-info.txt) Here is the system info

Added subscriber: @EAW

The 17mb is the lightcache data. Deleting it solves the crashing.

In #79737#996681, @EAW wrote:
The 17mb is the lightcache data. Deleting it solves the crashing.

Ah thanks, I haven't realized that it could be so big. Now I am unsure if this is valid bug I rarely come across lighting cache stuff. But I will keep this confirmed and monitor status.

> In #79737#996681, @EAW wrote: > The 17mb is the lightcache data. Deleting it solves the crashing. Ah thanks, I haven't realized that it could be so big. Now I am unsure if this is valid bug I rarely come across lighting cache stuff. But I will keep this confirmed and monitor status.

Added subscriber: @teldosas

Hey there! First comment here! :)

So, I was able to reproduce with the file provided. But, if I delete the lightcache data and I click "Bake Indirect Lighting" again the bug is no longer there. So, if I save the file and reopen it I can no longer reproduce the bug. Given all that, I suppose the bug is somewhere in the building of the lightcache and not in switching to render preview. In that case, I can't reproduce the bug with ec5f392087 on MacOS High Sierra.

Hey there! First comment here! :) So, I was able to reproduce with the file provided. But, if I delete the lightcache data and I click "Bake Indirect Lighting" again the bug is no longer there. So, if I save the file and reopen it I can no longer reproduce the bug. Given all that, I suppose the bug is somewhere in the building of the lightcache and not in switching to render preview. In that case, I can't reproduce the bug with ec5f392087 on MacOS High Sierra.

@teldosas you are probably correct, issue is with baking, so it would be best if we know how to create corrupted bake, but we could also maybe sanitize this crashy scenario.

This issue was referenced by 3be5697b88

This issue was referenced by 3be5697b889a9a3e677a504844e6b21eee0d753f

This issue was referenced by 4a82d792b0

This issue was referenced by 4a82d792b03b61baed6d70bed288291c72f1e3b8

Changed status from 'Confirmed' to: 'Resolved'

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

ERROR ACCESS VIOLATION when switching to evee rendered view #79737