# Dwirecon Segmentation fault: Invalid memory access

**URL:** <https://community.mrtrix.org/t/dwirecon-segmentation-fault-invalid-memory-access/4244>\
**Category:** Uncategorized\
**Created:** [October 30, 2020, 12:41pm UTC](https://community.mrtrix.org/t/dwirecon-segmentation-fault-invalid-memory-access/4244 "2020-10-30T12:41:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rsmith](https://community.mrtrix.org/user_avatar/community.mrtrix.org/rsmith/32/2672_2.png) [@rsmith](https://community.mrtrix.org/u/rsmith)\
**Post date:** [November 10, 2020, 2:26am UTC](https://community.mrtrix.org/t/dwirecon-segmentation-fault-invalid-memory-access/4244/2 "2020-11-10T02:26:29Z")

</div>

Welcome Colin!

Given that the SHARD recon is an external project and not yet a part of the _MRtrix3_ software, it may be more appropriate to post over on the relevant [issue list](https://github.com/dchristiaens/shard-recon/issues), as there’s a chance that it may be a problem specific to the contents of that project and not of the _MRtrix3_ back-end against which it is built.

Nevertheless, a couple of suggestions:

1. Run `top` in another terminal and monitor the RAM usage. If it approaches 100% prior to termination of the command, then your system does not possess sufficient RAM to process your data.

2. A `std::bad_alloc` can unfortunately mask the source of the problem if it is not as simple as insufficient RAM. The instructions [here](https://community.mrtrix.org/t/advanced-debugging-of-mrtrix3-binaries/2555) explain how to better isolate the source of the problem; however the runtime would be exceptionally long if running in debug mode.

3. This:

Cheers  
Rob

---

_[View the full topic](https://community.mrtrix.org/t/dwirecon-segmentation-fault-invalid-memory-access/4244)._