View Issue Details

IDProjectCategoryView StatusLast Update
0000516OpenFOAM[All Projects] Bugpublic2012-04-26 09:29
Reporteruser203Assigned Touser4 
Status resolvedResolutionno change required 
PlatformUNIXOSUbuntuOS Version 10.04.4 LTS
Product Version 
Fixed in Version 
Summary0000516: Some surface tools seg fault when the input is a binary STL output from Star-CCM+
DescriptionWhen trying to extract feature edges from a binary STL generated in STAR-CCM+, surfaceFeatureExtract would seg fault. An ascii STL from Star works fine, and if the binary STL is opened in another program (Rhino, Blender, etc) and re-saved, the binary stl will work again. The binary will also work if is re exported using surfaceConvert. (i.e. surfaceMeshConvert binaryCube.stl fixedBinaryCube.stlb)

This same issues also show up when using surfaceCheck, surfaceOrient and surfaceInteria, however they don't show up with snappyHexMesh or surfaceMeshInfo.

It appears that some surface utilities are doing the binary file reading differently than others.
Steps To ReproduceRun the following command:

surfaceFeatureExtract -includedAngle 150 constant/triSurface/binaryCube.stl binaryCube.eMesh

This will crash when you use the binaryCube.stl, but will succeed if asciiCube.stl isused instead. (Both files are in the attached zip file)
TagsNo tags attached.



2012-04-18 13:07 (582 bytes)


2012-04-19 17:00


This issue also seems to be present in binary stl output from SolidWorks as well.


2012-04-20 11:38


Do you know what is in the attribute?



2012-04-20 17:18


Ah, I see this issue, the header from the solid works one is:
"solid 1100752 Config 1zzz "

And the star ccm header is:
"solid PRO2STL version 1.0"

Looks like these programs are violating convention for binary files. Good catch, I didn't know about that convention.


2012-04-20 17:23


The header of your binary file goes

 solid PRO2STL version 1.0

This upsets the automatic detection. Use the .stlb extension instead to force binary reading (in commit fd03acd3e474aae4cae65a200ea973cf3ebabf4d).

From : A binary STL file has an 80 character header (which is generally ignored – but which should never begin with 'solid' because that will lead most software to assume that this is an ASCII STL file)

Issue History

Date Modified Username Field Change
2012-04-18 13:07 user203 New Issue
2012-04-18 13:07 user203 File Added:
2012-04-19 17:00 user203 Note Added: 0001277
2012-04-20 11:38 user4 Note Added: 0001278
2012-04-20 17:18 user203 Note Added: 0001279
2012-04-20 17:23 user4 Note Added: 0001280
2012-04-20 17:23 user4 Status new => closed
2012-04-20 17:23 user4 Assigned To => user4
2012-04-20 17:23 user4 Resolution open => fixed
2012-04-20 17:23 user4 Fixed in Version => 2.1.x
2012-04-26 09:29 user4 Status closed => resolved
2012-04-26 09:29 user4 Resolution fixed => no change required