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 to desktop on loading a decompiled Quake 2 map. #3886

Closed
eGax opened this issue Sep 22, 2021 · 0 comments · Fixed by #3981
Closed

Crash to desktop on loading a decompiled Quake 2 map. #3886

eGax opened this issue Sep 22, 2021 · 0 comments · Fixed by #3981
Labels
Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems
Milestone

Comments

@eGax
Copy link
Contributor

eGax commented Sep 22, 2021

System Information

A Linux TrenchBroom build of the current master branch. v2021.1-410-gc038098fa Release Linux

Expected Behavior

Not crash when having issues loading a map, but maybe throw an error window and go back to the Welcome window so the user can select another map.

Steps to Reproduce

Download this quake 2 inland3_decompiled.map.txt, remove the .txt, open into TrenchBroom on Linux as a quake 2 map(shouldn't matter if you don't have Q2 setup or not), and TB will crash to the desktop with no obvious errors or warnings but does still write the trenchbroom-crash.txt to the documents folder.

Crash Info

Reason: /trenchbroom-git/src/trenchbroom/common/src/Model/Polyhedron_Clip.h:189: Condition 'initialEdge != nullptr' failed: initialEdge is null

trenchbroom-crash.txt

I do understand decompiled maps are problematic, but still, it would be good if TB was robust enough to handle errors without crashing. Just to note the same map loads into Netradiant-custom with no issues.

Thank you very much!

@kduske kduske added Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems labels Sep 22, 2021
@kduske kduske added this to the 2022.2 milestone May 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants