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

Revit IFCs: Very slow processing and Out of memory exceptions #176

Closed
andyward opened this issue May 8, 2019 · 2 comments
Closed

Revit IFCs: Very slow processing and Out of memory exceptions #176

andyward opened this issue May 8, 2019 · 2 comments
Assignees
Labels
awaiting closure Issues that should be closed if we don't hear back on in a week bug Confirmed bug - system not working as intended
Milestone

Comments

@andyward
Copy link
Member

andyward commented May 8, 2019

Revit exporter 17.3.0.0 is outputting some IFC Geometry in a manner that's causing model processing to take hours & consume a lot of memory (resulting in crashes)

Assemblies and versions affected:

V5 Geometry v5.0.118

Minimal file to reproduce the issue:

See mp101-sw02-03-zz-a-mdi-xxxx-0100-0002.ifc provided privately by BT.

... which took 4 hours before crashing.

image

@andyward andyward added the bug Confirmed bug - system not working as intended label May 8, 2019
@andyward andyward added this to the 5.0.1 milestone May 8, 2019
@andyward andyward added the in progress Being worked on label May 8, 2019
@SteveLockley
Copy link
Member

This was caused by a huge polygonal mesh (representing louvres for a wall) with an opening cut into them. This is beyond the reasonable limits of Opencascade boolean operations and takes a considerable and unreasonable length of time. The operations are not really sensible, it has been trapped and a warning issued, the mesh geometry has been preserved to give some indication of location but the boolean has been aborted to allow the rest of the model to complete

@SteveLockley SteveLockley added awaiting closure Issues that should be closed if we don't hear back on in a week and removed in progress Being worked on labels May 13, 2019
@andyward
Copy link
Member Author

Confirmed fixed in Geometry 5.0.216-develop.

Took 16 mins, and memory usage was reasonable.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting closure Issues that should be closed if we don't hear back on in a week bug Confirmed bug - system not working as intended
Projects
None yet
Development

No branches or pull requests

2 participants