| T O P I C R E V I E W |
| Saint |
Posted - Aug 03 2007 : 05:41:27
There seems to be a memory problem.
OS: Win vista
Total Physical RAM: 4GB
MAybe windows problem not sure..
INPUT SUMMARY
Expansion order: 3
Number of partitioning levels: 9
Overall permittivity factor: 1
Total number of panels: 143580
Number of conductor panels: 143580
Number of dielectric interface panels: 0
Number of thin conductor on dielectric interface panels: 0
Number of conductors: 2
No expansions at level 9 (lowest)
fastcap: out of memory in file `C:\Documenti\Codice\FastSolvers\FastCap330_051224\fastcap\direct.c' at line 96
(NULL pointer on 128 byte request)
Total Memory Allocated: 1928600 kilobytes (brk = 0x42b050)
It's raining MEMS |
| 6 L A T E S T R E P L I E S (Newest First) |
| Enrico |
Posted - Feb 15 2012 : 23:33:53
You can try using FasterCap. It has a smaller memory footprint, and is able to use a smart out-of-core algoritm to overcome the physical RAM memory limit
Enrico |
| dave_royle |
Posted - Sep 06 2011 : 09:11:12
Windows uses a virtual address space of 4 GB, with 2 GB allocated to user-mode processes. User allocation can be increased to 3GB using the \3GB switch in boot.ini.
Dave |
| david2000abc |
Posted - Sep 05 2011 : 10:04:40
To allocate a matrix in the source field,there is a limit memory. Try to meth the structure with smaller number of panels.
mengmeng li |
| Akufen |
Posted - Jul 06 2009 : 11:24:31
Hi, I have the same problem but in an other line of code: at line 209.
----------------------------
GROUP1
Silicium.qui, conductor
title: `temp Si
'
outer permittivity: 3.9
number of panels: 6
number of extra evaluation points: 0
translation: (0 0 0)
GROUP2
graphene.qui, dielectric interface
title: `graphene
'
permittivities: 3.9 (inner) 1 (outer)
number of panels: 1
number of extra evaluation points: 2
translation: (0 0 0)
GROUP3
contacteur1.qui, dielectric interface
title: `contacteur1
'
permittivities: 3.9 (inner) 1 (outer)
number of panels: 6
number of extra evaluation points: 12
translation: (0 0 0)
GROUP4
contacteur2.qui, dielectric interface
title: `Contacteurs 2:
'
permittivities: 3.9 (inner) 1 (outer)
number of panels: 6
number of extra evaluation points: 12
translation: (0 0 0)
Date: Mon Jul 06 11:20:54 2009
fastcap: out of memory in file `C:\Documenti\Codice\FastSolvers\FastCap331_071231\fastcap\mulSetup.c' at line 209
(NULL pointer on 4096 byte request)
Total Memory Allocated: 1944509 kilobytes (brk = 0x428fe4)
placeq: 9 levels set up
-----------------------------------
Thanks |
| LarsSteffens |
Posted - May 04 2009 : 13:46:14
I get a similar error message running several problems i calculate. (Windows XP, 4GB physical memory)
Is there any solution to the described situation? I wonder why the program fails to get enough memory as there is "much" free memory left (little less than 1G). And if i reduce the complexity of the problem only slightly the program doesnt crash.
Thanks
------------------
INPUT SUMMARY
Expansion order: 10
Number of partitioning levels: 6
Overall permittivity factor: 1
Total number of panels: 11367
Number of conductor panels: 1347
Number of dielectric interface panels: 10020
Number of thin conductor on dielectric interface panels: 0
Number of conductors: 4
fastcap: out of memory in file `C:\Documenti\Codice\FastSolvers\FastCap331_071231\fastcap\direct.c' at line 96
(NULL pointer on 1176 byte request)
Total Memory Allocated: 2018043 kilobytes (brk = 0x428fe4)
|
| Enrico |
Posted - Aug 06 2007 : 00:32:32
I changed the title of the topic since the problem you are experiencing looks like a real out of memory issue, not a memory leak.
FastCap2 informs you that it has already allocated 1.926 Giga of memory and that an additional request to the OS (we don't know of how much memory) has been refused.
So Windows has not allowed FastCap2 to allocate more memory, even if you have 4G physical ram. This probably means that your other applications, including Windows, were already using all other memory, including the swap. Please note that, since we don't know how much additional memory was requested, we don't know at which limit the request was refused.
You can maybe verify the situation using the Windows 'Performance' panel, or a more specific application like the Process Viewer (distributed as a tool with MS Visual Studio)
Best Regards,
Enrico
|
