September 20, 2015 How do you handle OutOfMemoryError? | ||||
---|---|---|---|---|
| ||||
Here's my code: https://drive.google.com/file/d/0B3LYxKGJ4ZI_MV91SkxPVVlSOW8/view?usp=sharing I don't have access to a debugger. Run the code for a few minutes and it tends to crash with a core OutOfMemoryError. Any suggestions welcome including regularly cleaning up memory used. Thanks. |
September 20, 2015 Re: How do you handle OutOfMemoryError? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Enjoys Math | On Sunday, 20 September 2015 at 00:16:50 UTC, Enjoys Math wrote:
> Here's my code:
>
> https://drive.google.com/file/d/0B3LYxKGJ4ZI_MV91SkxPVVlSOW8/view?usp=sharing
>
> I don't have access to a debugger.
>
> Run the code for a few minutes and it tends to crash with a core OutOfMemoryError.
>
> Any suggestions welcome including regularly cleaning up memory used.
>
> Thanks.
Memory allocated with the GC (e.g. using new) will never be freed if a reference is kept to it. Are you accidentally or deliberately keeping a complete history of all programs? Are you allocating any memory from anywhere other than the GC?
What OS? How much RAM? Are you compiling with -m32 (and conversely what happens if you compile with -m64)?
|
Copyright © 1999-2021 by the D Language Foundation