Page MenuHome

Crash when entering wireframe mode with "single" color shading
Closed, ResolvedPublic

Description

System Information
Windows 10 64bit (Home)
Nvidia GeForce GTX 660 (opengl driver: 4.5.0 NVIDIA 388.13)

Blender Version
Broken: 2.80 (sub 24), hash: be0e58d980d

Short description of error
Blender crashes when entering wireframe mode when "single" color is selected in overlay popover. I found steps to crash it in edit mode consistently, but it also happens in object mode sometimes.

Exact steps for others to reproduce the error

  1. Open Blender
  2. Load factory settings
  3. Enter edit mode
  4. Leave edit mode
  5. Set "single" color in overlay popover

Repeat the following until crash (usually happens on first try, but not always):

  1. Enter edit mode
  2. Enter wireframe mode (crash happens here)
  3. Enter object mode
  4. Leave edit mode

Details

Type
Bug

Event Timeline

Sam (Sam200) renamed this task from Crash when entering wireframe with "single" color shading to Crash when entering wireframe mode with "single" color shading.
Philipp Oeser (lichtwerk) triaged this task as Confirmed, Medium priority.

Can confirm a crash here (linux, 970m with 396.45 drivers)

Is v_first_ofs supposed to be NULL here? backtrace:

1   ??                                                             0x7fffc91b4506 
2   ??                                                             0x7fffc91c5fe6 
3   ??                                                             0x7fffc8d7eb19 
4   GPU_batch_draw_range_ex               gpu_batch.c         631  0x25a7f3c      
5   draw_geometry_execute_ex              draw_manager_exec.c 850  0x2602328      
6   draw_geometry_execute                 draw_manager_exec.c 857  0x2602367      
7   draw_shgroup                          draw_manager_exec.c 1212 0x26034ce      
8   drw_draw_pass_ex                      draw_manager_exec.c 1285 0x26037c4      
9   DRW_draw_pass                         draw_manager_exec.c 1318 0x2603945      
10  workbench_forward_draw_scene          workbench_forward.c 613  0x267a221      
11  workbench_transparent_draw_background transparent_mode.c  66   0x263fb32      
12  drw_engines_draw_background           draw_manager.c      1013 0x25f77ba      
13  DRW_draw_render_loop_ex               draw_manager.c      1496 0x25f8953      
14  DRW_draw_view                         draw_manager.c      1409 0x25f8551      
15  view3d_draw_view                      view3d_draw.c       1259 0x1b2559f      
16  view3d_main_region_draw               view3d_draw.c       1280 0x1b2564f      
17  ED_region_do_draw                     area.c              529  0x1fa4435      
18  wm_draw_window_offscreen              wm_draw.c           537  0x19e8844      
19  wm_draw_window                        wm_draw.c           663  0x19e8dd8      
20  wm_draw_update                        wm_draw.c           817  0x19e92e4

@Clément Foucault (fclem) : mind having a look?

I can't get it to crash on linux + 960m.

v_first_ofs is supposed to be null pretty much every time. it is its default value.
@Philipp Oeser (lichtwerk) can you try running with --debug-gpu and also try running with v_first_ofs = NULL all the time.

Hi @Clément Foucault (fclem)!
P786 for the output of --debug-gpu (wall of text!)
P787 for the blender.crash.txt. (incl. op log repo steps)
(not sure these help..)

How would I "try running with v_first_ofs = NULL all the time"?

i have a version which is not crashing , or less crashing
here is its hash : b6c14437427

@Sam (Sam200) Could you test latest version to see if it is more stable?

It no longer crashes on the latest build. You guys are doing a good job on 2.8. I'm loving it.

Philipp Oeser (lichtwerk) closed this task as Resolved.Nov 5 2018, 9:35 AM

Lets close this then