|
[Sponsors] |
May 1, 2006, 05:28 |
CCM+ bad_alloc
|
#1 |
Guest
Posts: n/a
|
Does anyone know anything about "bad_alloc" errors in starccm+?? Occurs when I try and run the model. What could be causing this? How do I prevent it?! Thanks
|
|
May 1, 2006, 11:54 |
Re: CCM+ bad_alloc
|
#2 |
Guest
Posts: n/a
|
save your model after meshing. shutdown ccm+ and then restart it.
|
|
May 2, 2006, 12:38 |
Re: CCM+ bad_alloc
|
#3 |
Guest
Posts: n/a
|
bad_alloc is the standard c++ out of memory error. It probably failed to allocate enough space for the solution data.
As TG wrote, if you just generated the mesh, re-starting may allow you to proceed. If not, you may need more memory or a smaller mesh (fewer cells). |
|
May 2, 2006, 17:30 |
Re: CCM+ bad_alloc
|
#4 |
Guest
Posts: n/a
|
Now THAT sounds like something Micro$oft would offer you as a solution to bad code!
|
|
May 3, 2006, 12:33 |
Re: CCM+ bad_alloc
|
#5 |
Guest
Posts: n/a
|
try changing to explicit! and change the Courant no to very small for the begining say 0.1
|
|
May 5, 2006, 11:18 |
Re: CCM+ bad_alloc
|
#6 |
Guest
Posts: n/a
|
In fact this problem is worse on windows for various reasons. Try googling "heap fragmentation windows" ...
|
|
|
|