8000 Crash when deleting a duplicated entity with an angle value that's not in the same position as the original · Issue #2705 · TrenchBroom/TrenchBroom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when deleting a duplicated entity with an angle value that's not in the same position as the original #2705

Closed
ravey451 opened this issue Apr 9, 2019 · 1 comment · Fixed by #2706
Assignees
Labels
Prio:1 Highest priority: Crash or crippling bugs, features that enable new ways of working Type:Bug Errors and problems
Milestone

Comments

@ravey451
Copy link
ravey451 commented Apr 9, 2019

System Information

TrenchBroom 2019.5rc4 on Windows 10 (build 17763.437), 64-bit edition

Expected Behavior

The entity should be deleted.

Steps to Reproduce

  1. drag and drop an entity on to the viewport
  2. assign an angle value to the entity
  3. copy and paste, or duplicate and move the entity
  4. delete it

Crash Info

trenchbroom-crash.zip

@ericwa
Copy link
Collaborator
ericwa commented Apr 10, 2019

This is 2019.5rc4 and it's another AABB error:

OS: Windows 10 (build 17763), 64-bit edition
wxWidgets:
wxWidgets Library (wxMSW port)
Version 3.1.1 (Unicode: wchar_t, debug level: 1),
compiled at Feb 18 2018 18:36:35

Runtime version of toolkit used is 10.0.

GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce GTX 460/PCIe/SSE2
GL_VERSION: 4.6.0 NVIDIA 391.35
TrenchBroom Version: 2019.5
TrenchBroom Build: v2019.5-RC4 Release
Reason: Exception: AABB node not found with oldBounds [ ( 0 -26.5532 0 ) ( 144 24.3293 96 ) ]: 0A473F80
Stack trace:

@kduske kduske self-assigned this Apr 10, 2019
@kduske kduske added Prio:1 Highest priority: Crash or crippling bugs, features that enable new ways of working Type:Bug Errors and problems labels Apr 10, 2019
@kduske kduske added this to the 2019.5 milestone Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio:1 Highest priority: Crash or crippling bugs, features that enable new ways of working Type:Bug Errors and problems
Projects
None yet
3 participants
0