Bug 879665

Summary: sbcl fails if ulimit -v is used
Product: [Fedora] Fedora Reporter: Josh Cogliati <jrincayc>
Component: sbclAssignee: Rex Dieter <rdieter>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 21CC: green, matt, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 568753 Environment:
Last Closed: 2015-05-29 12:09:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Josh Cogliati 2012-11-23 15:49:51 UTC
This is still in Fedora 17.  

$ ulimit -S -v 1048576
$ sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 1073741824 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)
$ rpm -q sbcl
sbcl-1.0.57-1.fc17.x86_64


+++ This bug was initially created as a clone of Bug #568753 +++

Description of problem:
If a ulimit is set on the maximum amount of virtual memory that can be used, sbcl will always fail.

Version-Release number of selected component (if applicable):
sbcl-1.0.30-2.fc12.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. ulimit -S -v 1048576 #on a machine with 4GiB of RAM
2. sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 8589869056 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)

  
Actual results:
sbcl tries to allocate all the available ram.  

Expected results:
sbcl should check the ulimit on virtual ram, and not try and allocate more memory than that.  

Additional Info:
bug 548551 depends on this bug.

--- Additional comment from Matt McCutchen on 2010-04-13 21:02:45 EDT ---

Me too.  Trying to allocate 8 GiB of memory on startup isn't reasonable by any stretch of the imagination.  Enabling overcommit accounting (echo 2 >/proc/sys/vm/overcommit_memory) would also make it fail.

--- Additional comment from Bug Zapper on 2010-11-03 17:16:11 EDT ---


This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Rex Dieter on 2010-11-05 12:39:26 EDT ---

f13 i686 seems ok
f13 x86_64 problem still exists

--- Additional comment from Josh Cogliati on 2010-11-07 10:09:57 EST ---

f14 x86_64 problem still exists.  

ulimit -S -v 1048576
sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 8589869056 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)

sbcl-1.0.40-1.fc14.x86_64

Comment 1 Fedora End Of Life 2013-07-04 02:50:47 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Josh Cogliati 2013-07-04 13:35:07 UTC
Still exists in f18:

ulimit -S -v 1048576
sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 1073741824 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)
rpm -q sbcl
sbcl-1.1.2-1.fc18.x86_64

Comment 3 Fedora End Of Life 2013-12-21 09:29:21 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Josh Cogliati 2013-12-24 23:45:41 UTC
Still in Fedora 19 (and probably 20 as well, but I haven't upgraded yet)

$ ulimit -S -v 1048576
$ sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 1073741824 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)
$ rpm -q sbcl
sbcl-1.1.8-2.fc19.x86_64

Comment 5 Fedora End Of Life 2015-01-09 17:29:24 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Josh Cogliati 2015-01-10 01:25:34 UTC
This is still in Fedora 20.

$rpm -q sbcl
sbcl-1.1.12-1.fc20.x86_64
$ ulimit -S -v 1048576
$ sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 1073741824 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)

Comment 7 Fedora End Of Life 2015-05-29 08:49:10 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Josh Cogliati 2015-05-29 12:03:38 UTC
This is still in Fedora 21
$ rpm -q sbcl
sbcl-1.2.4-1.fc21.x86_64
$ ulimit -S -v 1048576
$ sbcl
mmap: Cannot allocate memory
ensure_space: failed to validate 1073741824 bytes at 0x1000000000
(hint: Try "ulimit -a"; maybe you should increase memory limits.)

Comment 9 Rex Dieter 2015-05-29 12:09:21 UTC
There's little point keeping this open forever, sbcl simply cannot work in that setup (feel free to poke sbcl upstream though).