Crash when enter in Edit Mode and try to a vertice. #63509

New Issue

Samuel Santos · 2019-04-12T02:37:17+02:00

Samuel Santos commented

2019-04-12 02:37:17 +02:00

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.
02 NO TEXTURE.blend
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: 009dbc2bc9
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)]

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. [02 NO TEXTURE.blend](https://archive.blender.org/developer/F6932725/02_NO_TEXTURE.blend) **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: `009dbc2bc9` 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)]

Samuel Santos commented

2019-04-12 02:37:17 +02:00

Added subscriber: @SamuelTelles

nBurn commented

2019-04-12 04:02:07 +02:00

Added subscriber: @nBurn

nBurn commented

2019-04-12 04:02:07 +02:00

Confirmed error with a recent 2.80 Win64 daily build:
blender-2.80-009dbc2bc9fb-win64
win64_cmake_vs2017 build# 800

Console log:

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

Box selection on the attached blend worked with an earlier 2.80 Win64 build:
blender-2.80-17c15798c35f-win64
win64_cmake_vs2017 build# 774

Confirmed error with a recent 2.80 Win64 daily build: `blender-2.80-009dbc2bc9fb-win64` `win64_cmake_vs2017 build# 800` Console log: ``` Read blend: ...\Downloads\02 NO TEXTURE.blend Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF61A4AE3E0 ``` Box selection on the attached blend worked with an earlier 2.80 Win64 build: `blender-2.80-17c15798c35f-win64` `win64_cmake_vs2017 build# 774`

0rAngE commented

2019-04-12 06:48:57 +02:00

Added subscriber: @0rAngE

0rAngE commented

2019-04-12 06:48:57 +02:00

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 (009dbc2bc9)
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"

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 commented

2019-04-12 07:45:27 +02:00

Added subscribers: @ZedDB, @mont29

nBurn commented

2019-04-12 07:45:27 +02:00

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

@ZedDB or @mont29 want to confirm?

I just tested with a fresh compile from source (at commit d1cda823e0) and do not get a crash (Windows x64). @ZedDB or @mont29 want to confirm?

Sebastian Parborg commented

2019-04-12 10:29:28 +02:00

Changed status from 'Open' to: 'Resolved'

Sebastian Parborg closed this issue

2019-04-12 10:29:28 +02:00

Sebastian Parborg self-assigned this 2019-04-12 10:29:28 +02:00

Sebastian Parborg commented

2019-04-12 10:29:28 +02:00

@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 #63467

@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 #63467

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash when enter in Edit Mode and try to a vertice. #63509