Page MenuHome

Weight paint mode with close up mesh, auto depth active, "show whole scene as transparent" shut down blender 2.8
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.80 (sub 61), branch: master, commit date: 2019-05-11 18:20, hash: ebc44aae9897,

Short description of error
With weight paint mode, when active mesh is close up in 3d view, (large enough ), if use "show whole scene as transparent" shut down blender

Exact steps for others to reproduce the error

  1. clear scene. load default cube and select cube.
  2. close up view, with mouse scroll, untill cube border edge is hidden by 3d view border.
  3. chage mode to weight paint.

(or just load attached cube scene)

4 . from 3d view top menu>toggle "whole scene transparent"

  1. it shut down blender. if not, scroll more to close up with perspective view, then toggle "whole scene transparent"

There seems some conditions to avoid this issue, eg not close up , etc, but when close up with weight paint mode,
and toggle " whole scene transparent" usually cause shut down. sometimes it happen immediately.

Blender crash.txt (with debug build)

Blender 2.80 (sub 61), Commit date: 2019-05-11 18:20, Hash ebc44aae9897

bpy.data.screens["Layout"].shading.show_xray = True # Property
bpy.ops.paint.weight_paint_toggle() # Operator

backtrace

27: BLI_system_backtrace - 0x229D2210
26: sig_handle_crash_backtrace - 0x225D9110
25: sig_handle_crash - 0x225D9160
24: windows_exception_handler - 0x225D93D0
23: UnhandledExceptionFilter - 0xD241BC40
22: memset - 0xD5A31580
21: _C_specific_handler - 0xD5A1B550
20: _chkstk - 0xD5A2F6C0
19: RtlWalkFrameChain - 0xD599C460
18: KiUserExceptionDispatcher - 0xD5A2E6E0
17: workbench_taa_view_updated - 0x239D7150
16: workbench_solid_view_update - 0x239927E0
15: DRW_notify_view_update - 0x238DA130
14: ED_render_scene_update - 0x25BC1E40
13: DEG::deg_editors_scene_update - 0x22B291D0
12: DEG_ids_check_recalc - 0x22B0A010
11: BKE_scene_graph_update_tagged - 0x22665520
10: wm_event_do_depsgraph - 0x2309E390
9: wm_event_do_refresh_wm_and_depsgraph - 0x2309E5A0
8: wm_event_do_notifiers - 0x2309E690
7: WM_main - 0x230805D0
6: main - 0x225D1D70
5: invoke_main - 0x263C2670
4: scrt_common_main_seh - 0x263C2420
3:
scrt_common_main - 0x263C2400
2: mainCRTStartup - 0x263C2730
1: BaseThreadInitThunk - 0xD31C4020
0: RtlUserThreadStart - 0xD5A03670

console
Settings loaded
18: BLI_system_backtrace - 0x229D2210
17: GPU_viewport_engine_data_create - 0x26077310
16: drw_viewport_engine_data_ensure - 0x238E0690
15: DRW_notify_view_update - 0x238DA130
14: ED_render_scene_update - 0x25BC1E40
13: DEG::deg_editors_scene_update - 0x22B291D0
12: DEG_ids_check_recalc - 0x22B0A010
11: BKE_scene_graph_update_tagged - 0x22665520
10: wm_event_do_depsgraph - 0x2309E390
9: wm_event_do_refresh_wm_and_depsgraph - 0x2309E5A0
8: wm_event_do_notifiers - 0x2309E690
7: WM_main - 0x230805D0
6: main - 0x225D1D70
5: invoke_main - 0x263C2670
4: scrt_common_main_seh - 0x263C2420
3:
scrt_common_main - 0x263C2400
2: mainCRTStartup - 0x263C2730
1: BaseThreadInitThunk - 0xD31C4020
0: RtlUserThreadStart - 0xD5A03670
BLI_assert failed: c:\myprograms\blender-git\blender\source\blender\gpu\intern\gpu_viewport.c:200, GPU_viewport_engine_data_create(), at '!"Too many draw engines enabled at the same time"'
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF6239D7173
Module : C:\myprograms\blender-git\build_windows_Release_x64_vc15_Debug\bin\Debug\blender.exe
Writing: I:\myfile\blender\Temp\blender.crash.txt
PS C:\myprograms\blender-git\build_windows_Release_x64_vc15_Debug\bin\Debug>

Event Timeline

When use factory default setting, this prolbem seems not happen.
(test with version: 2.80 (sub 62), branch: master, commit date: 2019-05-13 09:55, hash: 86650b01d873, type:

Then I check my preference setting, and find this clash haappen with use Preference>Auto depth mode

then Exact step to cause clash is

  1. Open user preference. > Navigation > Check Auto Depth option. my current setting is like that.

  1. Save preference, close blender, launch blender again.
  1. clear scene. load default cube and select cube.
  1. close up view, with mouse scroll, untill cube border edge is hidden by 3d view border.
  1. chage mode to weight paint mode.
  1. from 3d view top menu>toggle "whole scene transparent", it cause shut down. with factory setting.

takeshi funahashi (waitinfuture) renamed this task from Weight paint mode with close up mesh, "show whole scene as transparent" shut down blender 2.8 to Weight paint mode with close up mesh, auto depth active, "show whole scene as transparent" shut down blender 2.8.May 13 2019, 5:12 PM

I do not know if developer could not re-produce still, then add wmv file

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to 30.May 31 2019, 8:20 PM

Is this still an issue? I couldn't reproduce it in older or latest builds.

Broken: version: 2.80 (sub 72), branch: master, commit date: 2019-05-28 16:05, hash: `rB08005802ccb7
I test with factory set up, but auto depth active .(without it it seems not happen)
it always clash immediately, for me.

I still see same clash. now I up-date recent build then will report again. though I do not know if it only happen for windows 10 user or nvidia card.

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-05-31 21:41, hash: rBd5b813301a81

I test with recent build and it show same shut down.

takeshi funahashi (waitinfuture) raised the priority of this task from 30 to 90.Jun 2 2019, 2:08 AM
Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 80.Jun 11 2019, 4:32 PM

I think, this problem have been solved with recent up-dates.
I test with recent build, with keep same video driver (it was already up-dated) , now same scene not cause shut-down.

Test a few days ago, I saw same problem (cuase shut down) then I believe recent change solve this issue

takeshi funahashi (waitinfuture) changed the task status from Unknown Status to Resolved.Jun 24 2019, 9:00 AM