From bug-request at octave dot org Wed Jan 19 12:16:16 2005 Subject: Re: Serious memory leak in octave (this may be a duplicate bug report) From: Dan Nessett To: Per Persson CC: John Eaton , Date: Wed, 19 Jan 2005 12:05:51 -0600 Per, Moving to octave 2.1.50 doesn't fix the problem. As you can see from the following output from top, the number of pageouts greatly exceeds the number of pageins, which is another indication of a memory leak. Is there anyway I can help debug this problem? Is it possible this is a gcc 3.3 problem? I did not have the problem before I moved to it. Thanks, Dan P.S. I intend to move to 10.4 when it is released, but don't want to purchase 10.3 and then a few months later purchase 10.4. Processes: 54 total, 2 running, 52 sleeping... 140 threads 10:02:53 Load Avg: 0.52, 0.86, 0.92 CPU usage: 29.3% user, 5.0% sys, 65.7% idle SharedLibs: num = 90, resident = 5.78M code, 500K data, 220K LinkEdit MemRegions: num = 14122, resident = 902M + 1.38M private, 20.1M shared PhysMem: 83.4M wired, 619M active, 309M inactive, 1011M used, 12.8M free VM: 6.26G + 61.3M 14139(185) pageins, 468216(4621) pageouts PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE 21636 octave-2.1 56.9% 19:13.44 1 11 9963 891M- 2.71M+ 64.0M+ 2.52G+ 442 iTerm 3.3% 0:40.29 5 109 124 1.72M+ 2.40M+ 3.18M+ 116M On 1/18/05 1:13 PM, "Per Persson" wrote: > Not reproducible on Mac OS X 10.3.7 with octave 2.1.64. > > Dan, fink has 2.1.64 in the unstable branch, see > http://fink.sourceforge.net/pdb/package.php/octave. > > Ah, I just noticed that you run 10.2, the latest version of octave for > 10.2 is 2.1.50 (in the unstable branch). Could you test if that version > solves your problem? > > /Per > > On Jan 14, 2005, at 22:13, Dan Nessett wrote: > >> This may be a duplicate bug report. I got tangled up in emacs using >> bug_report and I don¹t know if it sent the email. >> >> When I attempt to display a vector of 800,000 elements, octave starts >> gobbling up virtual memory. The sequence of commands is: >> >> p=linspace(1,80000,800000)¹; >> p >> >> This is a test sequence. I discovered the bug when using plot() to >> plot two >> 800,000 vectors against each other. >> >> As you can see from the printout of ³top² below, octave consumes >> about 19 >> 1/2 minutes of cpu time processing this set of commands and its virtual >> space grows to 2.53 Gbytes. The printout from top is just after octave >> finishes the second command. This is on a 1.42GHz dual-processor G4 >> Mac with >> 1 Gbytes of memory running Mac OS X 10.2. >> >> PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE >> VSIZE >> 395 iTerm 7.9% 1:03.22 7 125 154 3.21M 2.66M+ 4.18M+ >> 120M+ >> 494 octave-2.1 3.8% 19:41.52 1 11 9965 884M+ 3.18M+ 127M- >> 2.53G+ > ------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------