Content
View differences
Updated by Eric Schubert about 2 years ago
### **Environment:**
Your OpenProject Version: 11.4.0 (BIM Edition, self-hosted)
**Update**: Retested on OpenProject Version 13.3+, still reproducible
Operating System / Browser / OpenProject language: Ubuntu Server 20.04 LTS / Google Chrome 94.0.4606.71 / Russian
### **Logs**
Attached.
The important bits are are
```text
Something went wrong: Error: Cannot create a string longer than 0x1fffffe8 characters
at Buffer.toString (buffer.js:778:17)
at JSON.parse (<anonymous>)
at convert (/home/wieland/.nodenv/versions/14.17.0/lib/node_modules/@xeokit/xeokit-gltf-to-xkt/gltf2xkt.js:65:23)
at async main (/home/wieland/.nodenv/versions/14.17.0/lib/node_modules/@xeokit/xeokit-gltf-to-xkt/gltf2xkt.js:56:24) {
code: 'ERR_STRING_TOO_LONG'
}
```
0x1fffffe8 (which is a hexadecimal number) is 536.870.888 as a decimal number, which makes sense as the current string size limit in Node.js is about 1GB.
### **Steps to reproduce:**
1. Go to BCF -> IFC models
2. Click on button "+ IFC model"
3. Select a BIG file (>190 MB) contains IFC4 model, click on button "Create"
### **Actual Behavior**
The file was uploaded successfully, processing status of that file is "In progress". Processing started and was never completed. The log file contains records about processing error on stage gltf2xkt. I think the problem is the string length limit in Node.js included in disribution. The error occurs on [line 65 in gltf2xkt.js file](https://github.com/xeokit/xeokit-gltf-to-xkt/blob/f21ef0944003f64640226646156e327de7d460c1/gltf2xkt.js#L67):
`const gltf = JSON.parse(gltfContent);`
Could you change this handling to get rid of this error?
### **Expected Behavior**
Processing completed successfully.
### Important hints
* `xeokit-gltf-to-xkt` tool is deprecated, possibly this behavior can be fixed by replacing the IFC2XKT conversion pipeline with https://github.com/xeokit/xeokit-convert
Your OpenProject Version: 11.4.0 (BIM Edition, self-hosted)
**Update**: Retested on OpenProject Version 13.3+, still reproducible
Operating System / Browser / OpenProject language: Ubuntu Server 20.04 LTS / Google Chrome 94.0.4606.71 / Russian
### **Logs**
Attached.
The important bits are
```text
Something went wrong: Error: Cannot create a string longer than 0x1fffffe8 characters
at Buffer.toString (buffer.js:778:17)
at JSON.parse (<anonymous>)
at convert (/home/wieland/.nodenv/versions/14.17.0/lib/node_modules/@xeokit/xeokit-gltf-to-xkt/gltf2xkt.js:65:23)
at async main (/home/wieland/.nodenv/versions/14.17.0/lib/node_modules/@xeokit/xeokit-gltf-to-xkt/gltf2xkt.js:56:24) {
code: 'ERR_STRING_TOO_LONG'
}
```
0x1fffffe8 (which is a hexadecimal number) is 536.870.888 as a decimal number, which makes sense as the current string size limit in Node.js is about 1GB.
### **Steps to reproduce:**
1. Go to BCF -> IFC models
2. Click on button "+ IFC model"
3. Select a BIG file (>190 MB) contains IFC4 model, click on button "Create"
### **Actual Behavior**
The file was uploaded successfully, processing status of that file is "In progress". Processing started and was never completed. The log file contains records about processing error on stage gltf2xkt. I think the problem is the string length limit in Node.js included in disribution. The error occurs on [line 65 in gltf2xkt.js file](https://github.com/xeokit/xeokit-gltf-to-xkt/blob/f21ef0944003f64640226646156e327de7d460c1/gltf2xkt.js#L67):
`const gltf = JSON.parse(gltfContent);`
Could you change this handling to get rid of this error?
### **Expected Behavior**
Processing completed successfully.
### Important hints
* `xeokit-gltf-to-xkt` tool is deprecated, possibly this behavior can be fixed by replacing the IFC2XKT conversion pipeline with https://github.com/xeokit/xeokit-convert