Skip to main content

Hi all, I have some troubles reading an ifc-File with FME 2018.1. I’m able to read all of the ifc-types except of IfcWindows and IfcWallStandardCase. When I read these feature types, I get memory issues and the workspace process fails with the message “Failed to free sufficient memory to reach the process usage limit”. The file is not that big (182MB) and I run it on a machine with 32GB RAM. I guess the problem is associated with the CSG Evaluation of the features. If I set this parameter to yes in the ifc-reader, then I get the memory issues right away when I start the workspace. If I set the parameter to no and run the workspace with certain transformers (like a GeometryValidator, VertexCounter,…) or the CSGEvaluator, I get the problems after a certain amount of features. As described in the reader documentation, the csg evaluation is performed, when it is required (“If the CSG evaluation is not performed in the IFC reader, FME will automatically perform the evaluation when it is required.”). With the VertexCounter I was able to filter out some invalid geometries, which had the fme_type “solid” but no geometry (VertexCount=0). Now I can read some more features, but after a certain amount, the process fails. Furthermore, the ifc reader does not respect the parameter “Start Feature”. Therefore I cannot split the reading process in multiple parts. Has anyone had similar issues and knows how to deal with it? Any advice what else I can try? Thank you in advance! Cheers, Manuela

I encountered the same issue immediately after upgrading FME version to 2108.0. I reported it to Safe support already (C136766, PR#83625, PR#83714), but it has not been fixed yet.

Currently, evaluating CSG solid process could cause memory overflow, crash the translation. There is no workaround, and it's one of fatal issues in my project. So terrible.Hope this will be fixed as soon as possible.


Hi @manu_uhlmann and @takashi,

 

 

This issue has a very high priority for us and I will post here once we have an update.

 

 

Brian

I encountered the same issue immediately after upgrading FME version to 2108.0. I reported it to Safe support already (C136766, PR#83625, PR#83714), but it has not been fixed yet.

Currently, evaluating CSG solid process could cause memory overflow, crash the translation. There is no workaround, and it's one of fatal issues in my project. So terrible.Hope this will be fixed as soon as possible.

Hi @takashi, @manu_uhlmann, and @fmelizard,

I am currently running into this problem, I also noticed that there has not been any response to this thread for over a year. But I am just wondering if this problem has been solved. I am currently also working with FME 2018.0. Will upgrading my version simply make the problem dissapear? or is there something else I should focus on?

 

Kind regards,

 

Daniel

Hi @takashi, @manu_uhlmann, and @fmelizard,

I am currently running into this problem, I also noticed that there has not been any response to this thread for over a year. But I am just wondering if this problem has been solved. I am currently also working with FME 2018.0. Will upgrading my version simply make the problem dissapear? or is there something else I should focus on?

 

Kind regards,

 

Daniel

Hi Daniel (@danielvp)

I just checked with the developers and the issue was fixed in 2019. The current release version will be fine to use. If you already have 2019 installed, just make sure it is greater than build 19130 and it will be OK.

Hope this helps

Mark

(for reference, the new ID number for the issue is FMEENGINE-16209)


Fixed in 2019 (build 19130 or greater).

New reference: FMEENGINE-16209


Fixed in 2019 (build 19130 or greater).

New reference: FMEENGINE-16209

Hi Mark (@mark2atsafe)

 

Thank you for that quick reply. Will make sure to try and upgrade my FME version.

Daniel


Fixed in 2019 (build 19130 or greater).

New reference: FMEENGINE-16209

Hi @mark2atsafe, happy to hear that. I found that these issues I reported before have been resolved with the current version of FME. Thanks!

  • C136766 PR#83625, PR#83714
  • C143126 FMEENGINE-59343

Fixed in 2019 (build 19130 or greater).

New reference: FMEENGINE-16209

I'm still experiencing something like this in 2019.1 (19608). While the memory issue appears to be addressed it appears the CSG Evaluation gets stuck or is at least very slow (at least with the sample I have. I have passed it on to support


Reply