# Complex geometry reading error in 0.13.2

**URL:** <https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436>\
**Category:** User Support\
**Created:** [November 4, 2022, 10:38am UTC](https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436 "2022-11-04T10:38:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexvalentine](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@alexvalentine](https://openmc.discourse.group/u/alexvalentine)\
**Post date:** [November 4, 2022, 10:38am UTC](https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436/1 "2022-11-04T10:38:45Z")

</div>

Hi,

I have recently installed 0.13.2 but ran into problems with more complex geometries. Simpler geometry descriptions still seem to be OK. You can see the error message below - the equivalent run in 0.13.1 on the same architecture proceeds to xs processing and runs fine.

![image](https://global.discourse-cdn.com/free1/uploads/openmc/original/2X/4/42aa36e58e5edbba4811025de49d626c6fda8e8e.png)

In running a different, also complex geometry, I face similar problems. Again, this is is fine in 0.13.1. Error reported in this case: ‘\*\*\* Error in `openmc’: corrupted size vs. prev\_size: 0x00000000057c7f30 \*\*\*’

Has anyone else faced similar issues? Unfortunately cannot share this exact geometry but should be able to create something if needs be.

Thanks,  
Alex

---

<div class="post-metadata">

**Author:** ![paulromano](https://yyz2.discourse-cdn.com/free1/user_avatar/openmc.discourse.group/paulromano/32/486_2.png) [@paulromano](https://openmc.discourse.group/u/paulromano)\
**Post date:** [November 4, 2022, 11:59am UTC](https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436/2 "2022-11-04T11:59:51Z")

</div>

Hi @alexvalentine. We did implement some geometry optimizations in version 0.13.2 for complex geometries, but it looks like something may have gone awry for your particular case. If you’re able to share a model on which this can be reproduced, we can try to get to the bottom of it.

---

<div class="post-metadata">

**Author:** ![alexvalentine](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@alexvalentine](https://openmc.discourse.group/u/alexvalentine)\
**Post date:** [November 9, 2022, 8:40pm UTC](https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436/3 "2022-11-09T20:40:31Z")

</div>

Hi Paul, sorry for the delay - I haven’t had chance to reproduce the error with another geometry however one thing I have found is that the same geometry converted with openmc conversion tool ([GitHub - openmc-dev/openmc\_mcnp\_adapter: Tool for converting MCNP input files to OpenMC classes/XML](https://github.com/openmc-dev/openmc_mcnp_adapter)) actually runs OK. The original models were converted with csg2csg… Tomorrow I should get chance to see what difference in the output models is the origin of this.

Alex

---

<div class="post-metadata">

**Author:** ![paulromano](https://yyz2.discourse-cdn.com/free1/user_avatar/openmc.discourse.group/paulromano/32/486_2.png) [@paulromano](https://openmc.discourse.group/u/paulromano)\
**Post date:** [November 10, 2022, 4:31am UTC](https://openmc.discourse.group/t/complex-geometry-reading-error-in-0-13-2/2436/4 "2022-11-10T04:31:21Z")

</div>

Interesting! Let me know if you’re able to narrow it down to a particular cell definition. Even if there’s an error in the definition, ideally OpenMC should abort a little more gracefully than what you observed, so we may have some bug fixing to do.