# \*ERROR in u\_calloc: error allocating memory **URL:** \ **Category:** Uncategorized\ **Created:** [July 6, 2023, 7:09am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728 "2023-07-06T07:09:09Z")\ **Posts on this page:** 12\ **Page:** 2
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 7, 2023, 12:53am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/21 "2023-09-07T00:53:26Z")
@rsmith What do you mean by that? Do you have any changes to my process regarding the use of \*restart,read? Because I always felt like my operation wasn’t official. (delete the.rin file, change the resulting.rout file to a.rin file as the start file for the next.inp,) ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 7, 2023, 12:55am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/22 "2023-09-07T00:55:10Z")
@jbr So how do I modify my program? I’ve been feeling a little weird about my use of \*restart,read (delete the.rin file, change the resulting.rout file to a.rin file as the start file for the next.inp), but I don’t know any other proper uses for \*restart. ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [September 7, 2023, 1:01am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/23 "2023-09-07T01:01:17Z")
I would do the following: 1. Start by creating a new mesh with only quad elements (S8 as @rsmith suggested). 2. Make sure that nodes and elements are sequential and that no gaps between node/element numbers exist. 3. Do a quick modal extraction, free-free or fixed, to make sure the model behaves as expected. 4. Run your simulation as you have done in the past… ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 7, 2023, 1:20am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/24 "2023-09-07T01:20:50Z")
@jbr Then I think my use of inp and \*restart should be correct, because after 180+ runs, the memory allocation problem appears later… ---
**Author:** ![xyont](https://yyz2.discourse-cdn.com/free1/user_avatar/calculix.discourse.group/xyont/32/3553_2.png) [@xyont](https://calculix.discourse.group/u/xyont)\ **Post date:** [September 7, 2023, 3:43pm UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/25 "2023-09-07T15:43:48Z")
> [@Phonix](#): > > **CalculiX Version 2.20, Copyright(C) 1998-2022 Guido Dhondt** > CalculiX comes with ABSOLUTELY NO WARRANTY. This is free > software, and you are welcome to redistribute it under > certain conditions, see gpl.htm did it have problems in latest versions also? ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [September 7, 2023, 10:03pm UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/26 "2023-09-07T22:03:53Z")
I would say that may be true but then something else is creating the issue, it is not a CalculiX problem… ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 8, 2023, 1:03am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/27 "2023-09-08T01:03:38Z")
I don’t know. I haven’t tried the new version yet,0.0 ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 8, 2023, 1:05am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/28 "2023-09-08T01:05:14Z")
Then I’ll try to find out what might have caused it ---
**Author:** ![Disla](https://yyz2.discourse-cdn.com/free1/user_avatar/calculix.discourse.group/disla/32/3548_2.png) [@Disla](https://calculix.discourse.group/u/Disla)\ **Post date:** [September 8, 2023, 6:21am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/29 "2023-09-08T06:21:03Z")
Not sure if this could help but what about using OP=NEW to clean previous \*CLOAD before the \*INCLUDE, INPUT=force.txt "Applying a point load at a node in a direction for which a point load was specified in a previous step replaces this point load, otherwise **it is added**. The parameter OP=NEW on the \*CLOAD card removes all previous point loads." Not really sure about its effect on allocation for the geometric BC as it’s a dynamic analysis . ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 11, 2023, 6:15am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/30 "2023-09-11T06:15:50Z")
I’ve tried, but it hasn’t worked ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 25, 2023, 1:38am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/31 "2023-09-25T01:38:33Z")
I have tried the new version, but the problem still occurs, and I found that the problem is not caused by too little memory. I only got so far with the 2T of memory on my supercalculator that I got this error. ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [September 25, 2023, 1:39am UTC](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728/32 "2023-09-25T01:39:38Z")
I found that the problem was not caused by too little memory. I only got so far with the 2T of memory on my supercalculator that I got this error. So could this problem be caused by some parameters set too small in calculix source code? [Previous page](https://calculix.discourse.group/t/error-in-u-calloc-error-allocating-memory/1728.md?page=1)