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 with ClipPlaneSet::ClipPlaneSetSectionPolyface in DPTA on windows #957

Open
mathieu-lemuzic opened this issue Jan 9, 2025 · 2 comments · May be fixed by #959
Open

Crash with ClipPlaneSet::ClipPlaneSetSectionPolyface in DPTA on windows #957

mathieu-lemuzic opened this issue Jan 9, 2025 · 2 comments · May be fixed by #959
Assignees
Labels
bug Something isn't working geometry

Comments

@mathieu-lemuzic
Copy link
Contributor

I'm experiencing a crash when a section cut is produced in DPTA with DemoHouse.bim in view Section Cut.

The exception is either silent or can cause the whole itwinjs backend process to crash depending on the machine / OS, so far only windows has been tested.

When testing with DPTA please ensure that the tile cache is cleared between runs otherwise the section cut will not be produced in the following runs.

Below is the callstack:
Image

And here is the line that causes the crash:
Image

The DPTA config file:
config.json

Link to the imodel:
\bentley.com\shares\Temp\mlemuzic\DemoHouse.bim

@mathieu-lemuzic mathieu-lemuzic added bug Something isn't working geometry labels Jan 9, 2025
@dassaf4
Copy link
Member

dassaf4 commented Jan 9, 2025

Inputs to PolyfaceQuery::PlaneSlice: mesh-small-open.txt, plane.origin (0,0,-54.674777215387010), plane.normal (0,0,-1), formRegions=true, markEdgeFractions=false, skipOnPlaneFacets=false.

@dassaf4 dassaf4 linked a pull request Jan 10, 2025 that will close this issue
@dassaf4
Copy link
Member

dassaf4 commented Jan 10, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working geometry
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants