# Still problem in memory alloc **URL:** \ **Category:** Uncategorized\ **Created:** [October 5, 2023, 7:36am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858 "2023-10-05T07:36:37Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 5, 2023, 7:36am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/1 "2023-10-05T07:36:37Z")
Dear Calculix Support, I have updated the Pardiso Solver for run my Thermo-Structural Analysis but it seems that the allocation memory issue is still there. Here below is reported the error message: " Determining the structure of the matrix: Using up to 1 cpu(s) for setting up the structure of the matrix. number of equations 1151429 number of nonzero lower triangular matrix elements 15079962 \*ERROR in u\_calloc: error allocating memory variable=xstateini, file=nonlingeo.c, line=833, num=1122431908, size=8 Job failed - no results exist. Process elapsed time: 61.881 s " ---
**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\ **Post date:** [October 5, 2023, 8:54am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/2 "2023-10-05T08:54:23Z")
Aren’t you using parallel processing ? Which version of CalculiX ? Did you try reducing the mesh density ? ---
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 5, 2023, 11:43am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/3 "2023-10-05T11:43:26Z")
I’m submitting the job on a laptop, probably it work on more than 1 cpu. Calculix version is those related to 1.3.5 Prepomax. I’m working on a benchmark for comparison with Abaqus, so I can’t modifiy the mesh density because this will affect the results for the final scope that is the comparison. Thanks & Regards ---
**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\ **Post date:** [October 5, 2023, 12:15pm UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/4 "2023-10-05T12:15:21Z")
Check how many CPUs you have (Task Manager → Performance) and enter that number in _Tools → Settings → CalculiX → Number of processors_ in PrePoMax. ---
**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\ **Post date:** [October 5, 2023, 8:39pm UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/5 "2023-10-05T20:39:58Z")
check out this thread, maybe you need to use CCX i8 version ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [October 5, 2023, 9:51pm UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/6 "2023-10-05T21:51:02Z")
Can you share the model? I want to run it and check with gdb… ---
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 11, 2023, 9:37am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/7 "2023-10-11T09:37:34Z")
I tried with the maximum CPU (8) but still same error ---
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 11, 2023, 9:39am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/8 "2023-10-11T09:39:47Z")
Sorry, could yo explain better what you mean, I tried with the version named CalculiX Version 2.20. ---
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 11, 2023, 9:41am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/9 "2023-10-11T09:41:58Z")
No unfortunatelly I can’t share this model outside my organization. What you mean for check with gdb? ---
**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:** [October 11, 2023, 10:47am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/10 "2023-10-11T10:47:43Z")
Could you reference the benchmark?. Is it based on some Abaqus validation file? Have you been able to solve with a smaller mesh. Just to discard a problem on the \*inp set up.? ---
**Author:** ![Antonio\_Crupi](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@Antonio\_Crupi](https://calculix.discourse.group/u/Antonio_Crupi)\ **Post date:** [October 11, 2023, 11:16am UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/11 "2023-10-11T11:16:04Z")
No is it an internal Benchmark for compare the results between the two solver. Thanks for the suggestion, I’ll check with the reduction of the size model in order to fix the issue. Thanks ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [October 11, 2023, 12:38pm UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/12 "2023-10-11T12:38:14Z")
Its GNU’s debugger [https://www.sourceware.org/gdb/](https://www.sourceware.org/gdb/) ---
**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\ **Post date:** [October 11, 2023, 6:25pm UTC](https://calculix.discourse.group/t/still-problem-in-memory-alloc/1858/13 "2023-10-11T18:25:03Z")
sorry, I missed the link: [Error allocating memory](https://calculix.discourse.group/t/error-allocating-memory/1429)