[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Octave Memory Issue
From: |
John W. Eaton |
Subject: |
Octave Memory Issue |
Date: |
Mon, 10 Mar 2008 20:26:40 -0400 |
On 10-Mar-2008, John W. Eaton wrote:
| On 10-Mar-2008, Obsessive MathsFreak wrote:
|
| | Octave gobbles up and will not release memory allocated in functions
| | after access in a for loop
| |
| | Kernel:
| | Ubuntu 7.10 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007
| | x86_64 GNU/Linux
| |
| | Octave(From Ubuntu Repositories):
| | GNU Octave, version 2.1.73 (x86_64-pc-linux-gnu).
| |
| | Steps to reproduce(CAUTION may hang due to swappiness):
| |
| | $ octave < dud.m
| |
| | And watch the memory burn away.
| |
| | "clear" helps, but not completely. And no, doing away with the for
| | loops is not possible. This is a simplified example of a much more
| | complex function.
| |
| | Remove the line inside the nested for loops to see the memory usages
difference.
| |
| | I'd like to know of any octave command or setting that forces garbage
| | collection on the system to prevent this.
|
| Although I can reproduce this problem with Octave 2.1.73, I have no
| plans to investigate or fix it since 2.1.73 is obsolete.
|
| The current
| stable version is 3.0.0, and I can't re
|
| I can't
Sorry, this message was accidentally sent before I finished editing
it.
I mean to write that I can't reproduce the problem with the current
stable version, 3.0.0, and that I strongly encourage you to upgrade.
Also, the place to report bugs is the address@hidden list.
jwe