Crash rendering eevee motion blur on camera change #78545

New Issue

RedMser · 2020-07-02T20:33:17+02:00

RedMser commented

2020-07-02 20:33:17 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-01 20:17, hash: 52b125a790

Short description of error
When rendering a frame where camera changes (marker bound to camera) with motion blur enabled in eevee, Blender crashes.

Exact steps for others to reproduce the error

Create two cameras and two markers
Bind each camera to a marker
Enable motion blur in eevee
Go to the second marker and render the frame

Simple reproduction file (simply load and press F12 to render): mbcrash.blend

Stacktrace:


ExceptionCode         : EXCEPTION_ACCESS_VIOLATION
Exception Address     : 0x00007FF7972AE557
Exception Module      : blender.exe
Exception Flags       : 0x00000000
Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000001
	Parameters[1] : 0x0000000000000010


Stack trace:
blender.exe         :0x00007FF7972AE4E0  EEVEE_lightprobes_cache_init
blender.exe         :0x00007FF7972B4730  EEVEE_render_cache_init
blender.exe         :0x00007FF7972B6990  eevee_render_to_image
blender.exe         :0x00007FF79729F640  DRW_render_to_image
blender.exe         :0x00007FF79A7C9A40  RE_engine_render
blender.exe         :0x00007FF79A7D2530  do_render
blender.exe         :0x00007FF79A7D2750  do_render_composite
blender.exe         :0x00007FF79A7D25A0  do_render_all_options
blender.exe         :0x00007FF79A7CFE00  RE_RenderFrame
blender.exe         :0x00007FF797D953D0  render_startjob
blender.exe         :0x00007FF7971C1590  do_job_thread
blender.exe         :0x00007FF79B208A00  _ptw32_threadStart
ucrtbase.dll        :0x00007FFCC7B30D30  beginthreadex
KERNEL32.DLL        :0x00007FFCC94D7BC0  BaseThreadInitThunk
ntdll.dll           :0x00007FFCCAB6CEB0  RtlUserThreadStart

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-01 20:17, hash: `52b125a790` **Short description of error** When rendering a frame where camera changes (marker bound to camera) with motion blur enabled in eevee, Blender crashes. **Exact steps for others to reproduce the error** - Create two cameras and two markers - Bind each camera to a marker - Enable motion blur in eevee - Go to the second marker and render the frame Simple reproduction file (simply load and press F12 to render): [mbcrash.blend](https://archive.blender.org/developer/F8660257/mbcrash.blend) Stacktrace: ``` ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF7972AE557 Exception Module : blender.exe Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000001 Parameters[1] : 0x0000000000000010 Stack trace: blender.exe :0x00007FF7972AE4E0 EEVEE_lightprobes_cache_init blender.exe :0x00007FF7972B4730 EEVEE_render_cache_init blender.exe :0x00007FF7972B6990 eevee_render_to_image blender.exe :0x00007FF79729F640 DRW_render_to_image blender.exe :0x00007FF79A7C9A40 RE_engine_render blender.exe :0x00007FF79A7D2530 do_render blender.exe :0x00007FF79A7D2750 do_render_composite blender.exe :0x00007FF79A7D25A0 do_render_all_options blender.exe :0x00007FF79A7CFE00 RE_RenderFrame blender.exe :0x00007FF797D953D0 render_startjob blender.exe :0x00007FF7971C1590 do_job_thread blender.exe :0x00007FF79B208A00 _ptw32_threadStart ucrtbase.dll :0x00007FFCC7B30D30 beginthreadex KERNEL32.DLL :0x00007FFCC94D7BC0 BaseThreadInitThunk ntdll.dll :0x00007FFCCAB6CEB0 RtlUserThreadStart ```

RedMser commented

2020-07-02 20:33:17 +02:00

Added subscriber: @RedMser

RedMser changed title from ~~Crash rendering eevee object motion blur on camera change~~ to Crash rendering eevee motion blur on camera change

2020-07-02 20:33:53 +02:00

RedMser commented

2020-07-02 20:39:47 +02:00

Changed status from 'Needs Triage' to: 'Archived'

RedMser closed this issue

2020-07-02 20:39:47 +02:00

RedMser commented

2020-07-02 20:39:47 +02:00

Just noticed this is a duplicate of #78452