Page MenuHome

Crash when enter in Edit Mode and try to a vertice.
Closed, ResolvedPublic


Crash when enter in Edit Mode and try to select a single vertice or multiple using box select. Doesn't crash using "select all" command.

Crash in new objects and in existing ones.

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.94

Blender Version
Broken: version: 2.80 (sub 55), branch: blender2.7, commit date: 2019-04-09 18:12, hash: rB009dbc2bc9fb
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]



Event Timeline

nBurn (nBurn) lowered the priority of this task from Needs Triage by Developer to Confirmed, High.EditedApr 12 2019, 4:02 AM
nBurn (nBurn) added a subscriber: nBurn (nBurn).

Confirmed error with a recent 2.80 Win64 daily build:
win64_cmake_vs2017 build# 800

Console log:

Read blend: ...\Downloads\02 NO TEXTURE.blend
Address : 0x00007FF61A4AE3E0

Box selection on the attached blend worked with an earlier 2.80 Win64 build:
win64_cmake_vs2017 build# 774

The culprit is X-Ray set to =1:
(VIEW3D_PT_shading) Shading (DropDown) > X-Ray (Enabled, and set to =1)

I was just about to post a bug report, and did a search and found this.
I'll paste here what I had already written:

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35

Blender Version
Broken: version: 2.80 (009dbc2bc9fb)
Worked: Haven't used buildbots in about 4 weeks, it was fine before that!

Short description of error
(VIEW3D_PT_shading) Shading (DropDown) > X-Ray (Enabled, and set to =1)
This crashes blender when using BoxSelect in EditMode (Vertex).
In addition, it also makes some Vertices of the (Default) Cube unselectable.
All this happens only when X-Ray is set fully to =1

Exact steps for others to reproduce the error
Using the default startup:

  • Boot blender
  • Set X-Ray fully to =1
    • (VIEW3D_PT_shading) Shading (DropDown) > X-Ray (Enabled, and set to =1)
  • Select the default Cube > Enter EditMode (you will be in VertexMode)
  • Using LMB Drag try to do a BoxSelect. This will more often than not result in an instant crash. Same thing happens if you invoke BoxSelect with "B"
nBurn (nBurn) raised the priority of this task from Confirmed, High to Needs Triage by Developer.Apr 12 2019, 7:45 AM

I just tested with a fresh compile from source (at commit rBd1cda823e0a8) and do not get a crash (Windows x64).

@Sebastian Parborg (zeddb) or @Bastien Montagne (mont29) want to confirm?

Sebastian Parborg (zeddb) closed this task as Resolved.EditedApr 12 2019, 10:29 AM
Sebastian Parborg (zeddb) claimed this task.

@nBurn (nBurn) do not set the priority yourself. You can always ping one of the developers, otherwise this bug report would have been missed. EDIT: Sorry didn't know you had commit rights (so a dev). Anyways you should always assign someone to the bug. Otherwise it will take a lot longer until anyone takes a look at it.

Thankfully someone else reported the same issue and I fixed it yesterday T63467