# I can't help but think debugging memory allocations shouldn't be this hard

**URL:** https://discourse.julialang.org/t/i-cant-help-but-think-debugging-memory-allocations-shouldnt-be-this-hard/105042
**Category:** General Usage
**Created:** [October 17, 2023, 2:05am UTC](https://discourse.julialang.org/t/i-cant-help-but-think-debugging-memory-allocations-shouldnt-be-this-hard/105042 "2023-10-17T02:05:14Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![vchuravy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vchuravy/32/8_2.png) [@vchuravy](https://discourse.julialang.org/u/vchuravy)
#### Post date: [October 17, 2023, 11:12pm UTC](https://discourse.julialang.org/t/i-cant-help-but-think-debugging-memory-allocations-shouldnt-be-this-hard/105042/18 "2023-10-17T23:12:55Z")

</div>

> [@PetrKryslUCSD](#):
>
> . But there was only a mention of the integers, nothing about boxing matrices. I will check out what you suggested. Thanks.

The type information of CSys being unavailable would cause a slower way of calling `updatecsmat!` which requires all the integers to be boxed. The array is already a boxed value.

---

_[View the full topic](https://discourse.julialang.org/t/i-cant-help-but-think-debugging-memory-allocations-shouldnt-be-this-hard/105042)._