Using stacksize() function to increase virtual memory in Ubuntu 7.10's scilab 4.1.1 results in excessive memory allocation. In some cases memory is continually allocated until system slows to a crawl, swapping.
Ubuntu 7.10
Scilab package: 4.1.1-1
In comparison, scilab 4.1.2 downloaded as a binary from scilab.org works fine. A previously downloaded 4.1.1 version of Scilab from scilab.org also worked fine (used on an older version of Ubuntu, 6.10 LTS I believe) so it is not fundamentally a scilab problem.
Here are some allocation examples between the two (total virtual process size reported). Stacksize() function takes a numeric argument which is the number of 8-byte doubles to increase stack allocation by, so stacksize(40000000) should allocate 320 MB to the stack. In these examples, no code is being run or data loaded; just the command line shell is started and the stacksize() command is executed. 4.1.2 produces the expected virtual size; 4.1.1 is roughly double under no activity. With significant code running, my observation is that Ubuntu's 4.1.1 scilab continues to allocate memory well beyond the stacksize() numbers shown below, just doesn't seem to stop allocating (but that's a guess). As a result, Ubutnu's scilab 4.1.1 is unusable.
stacksize() 4.1.1 (Ubuntu pkg) 4.1.2 (scilab.org binary release)
=====================================================
10000000 180 MB 96.5 MB
20000000 337 MB 174 MB
40000000 649 MB 331 MB
100000000 1.43 GB 800 MB
Recommend: fix (presumed) configuration issue with Ubuntu's scilab 4.1.1 package.
-- Bug description --
Reported in the Ubuntu bug tracker:
https:/
--
Using stacksize() function to increase virtual memory in Ubuntu 7.10's scilab 4.1.1 results in excessive memory allocation. In some cases memory is continually allocated until system slows to a crawl, swapping.
Ubuntu 7.10
Scilab package: 4.1.1-1
In comparison, scilab 4.1.2 downloaded as a binary from scilab.org works fine. A previously downloaded 4.1.1 version of Scilab from scilab.org also worked fine (used on an older version of Ubuntu, 6.10 LTS I believe) so it is not fundamentally a scilab problem.
Here are some allocation examples between the two (total virtual process size reported). Stacksize() function takes a numeric argument which is the number of 8-byte doubles to increase stack allocation by, so stacksize(40000000) should allocate 320 MB to the stack. In these examples, no code is being run or data loaded; just the command line shell is started and the stacksize() command is executed. 4.1.2 produces the expected virtual size; 4.1.1 is roughly double under no activity. With significant code running, my observation is that Ubuntu's 4.1.1 scilab continues to allocate memory well beyond the stacksize() numbers shown below, just doesn't seem to stop allocating (but that's a guess). As a result, Ubutnu's scilab 4.1.1 is unusable.
stacksize() 4.1.1 (Ubuntu pkg) 4.1.2 (scilab.org binary release)
=======
10000000 180 MB 96.5 MB
20000000 337 MB 174 MB
40000000 649 MB 331 MB
100000000 1.43 GB 800 MB
Recommend: fix (presumed) configuration issue with Ubuntu's scilab 4.1.1 package.
---
-- Scilab error message --
-- How to reproduce the bug --