Page MenuHome

ERROR ACCESS VIOLATION when switching to evee rendered view
Closed, ResolvedPublic


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

Blender Version
Broken: 2.83 LTS, 2.90, rB50b435cbaaa0
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

Event Timeline

caleb (lysol) updated the task description. (Show Details)
Julian Mohr (Jules) changed the task status from Needs Triage to Needs Information from Developers.EditedAug 12 2020, 7:08 PM

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.

Richard Antalik (ISS) changed the task status from Needs Information from Developers to Confirmed.Aug 13 2020, 2:09 PM

File is very complex and it would be best if @caleb (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]
Richard Antalik (ISS) renamed this task from ERROR ACCESS VIOLATION when switching from cycles to evee rendered view to ERROR ACCESS VIOLATION when switching to evee rendered view.Aug 13 2020, 2:13 PM
Richard Antalik (ISS) updated the task description. (Show Details)

I've removed every object in the scene, and it still crashes. Now blender is writing out this crash file. @Richard Antalik (ISS). I've attached the blend file with no objects in it

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?

Here is the system info

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

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.

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 rBec5f39208785c1 on MacOS High Sierra.

@Aristotelis Dossas (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.