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 moving camera in 3D #37881

Closed
saberraz opened this issue Jul 20, 2020 · 4 comments
Closed

Crash when moving camera in 3D #37881

saberraz opened this issue Jul 20, 2020 · 4 comments
Labels
3D Relates to QGIS' 3D engine or rendering Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@saberraz
Copy link
Contributor

Output from gdb:

camera position got NaN!
camera position got NaN!
[Thread 0x7fff437fe700 (LWP 292816) exited]
ERROR 1: IllegalArgumentException: Points of LinearRing do not form a closed linestring
ERROR 1: IllegalArgumentException: Points of LinearRing do not form a closed linestring
Fatal: ASSERT: "mState == QgsChunkNode::Loaded" in file ../src/3d/chunks/qgschunknode_p.cpp, line 181
QGIS died on signal -1[Detaching after fork from child process 292854]

@saberraz saberraz added Bug Either a bug report, or a bug fix. Let's hope for the latter! 3D Relates to QGIS' 3D engine or rendering labels Jul 20, 2020
@saberraz
Copy link
Contributor Author

I try to reproduce it with some public data, but the issue disappeared when I transformed all my layers to a single projected CRS. In the problematic project, the 3D vectors were in EPSG:4326 raster in EPSG:27700 and canvas was in EPSG:3857

@PeterPetrik
Copy link
Contributor

Hi @saberraz,

  • which version of QGIS?
  • which OS?
  • can you try to use tools to find features with invalid geometry?
    thanks

@PeterPetrik PeterPetrik added the Feedback Waiting on the submitter for answers label Oct 9, 2020
@github-actions
Copy link

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Dec 22, 2020
@github-actions
Copy link

While we hate to see this happen, this Issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3D Relates to QGIS' 3D engine or rendering Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

3 participants