Description of problem: From GNOME terminal, as root, ran: fedup --network 18 It downloaded around 2000 packages, then failed: Traceback (most recent call last): File "/bin/fedup", line 330, in <module> main(args) File "/bin/fedup", line 275, in main pkgs = download_packages(f) File "/bin/fedup", line 61, in download_packages f.download_packages(updates, callback=output.DownloadCallback()) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 209, in download_packages updates = self._downloadPackages(callback) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 6105, in _downloadPackages probs = self.downloadPkgs(dlpkgs) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2313, in downloadPkgs urlgrabber.grabber.parallel_wait() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2259, in parallel_wait start(opts, 1) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2148, in start dl.start(opts) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2080, in start dl = _ExternalDownloader() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2003, in __init__ stdout = subprocess.PIPE, File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1143, in _execute_child self.pid = os.fork() OSError: [Errno 12] Cannot allocate memory System is eee pc 901, 1GB RAM, no swap enabled. Version-Release number of selected component: fedup-0.7.2-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: /usr/bin/python /bin/fedup --network 18 kernel: 3.6.11-1.fc17.i686 backtrace: :subprocess.py:1143:_execute_child:OSError: [Errno 12] Cannot allocate memory : :Traceback (most recent call last): : File "/bin/fedup", line 330, in <module> : main(args) : File "/bin/fedup", line 275, in main : pkgs = download_packages(f) : File "/bin/fedup", line 61, in download_packages : f.download_packages(updates, callback=output.DownloadCallback()) : File "/usr/lib/python2.7/site-packages/fedup/download.py", line 209, in download_packages : updates = self._downloadPackages(callback) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 6105, in _downloadPackages : probs = self.downloadPkgs(dlpkgs) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2313, in downloadPkgs : urlgrabber.grabber.parallel_wait() : File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2259, in parallel_wait : start(opts, 1) : File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2148, in start : dl.start(opts) : File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2080, in start : dl = _ExternalDownloader() : File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 2003, in __init__ : stdout = subprocess.PIPE, : File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ : errread, errwrite) : File "/usr/lib/python2.7/subprocess.py", line 1143, in _execute_child : self.pid = os.fork() :OSError: [Errno 12] Cannot allocate memory : :Local variables in innermost frame: :executable: '/usr/libexec/urlgrabber-ext-down' :shell: False :errpipe_read: 175 :p2cread: 34 :errread: None :startupinfo: None :close_fds: False :c2pread: 173 :args: ['/usr/libexec/urlgrabber-ext-down'] :gc_was_enabled: True :errwrite: None :cwd: None :self: <subprocess.Popen object at 0xc8e484c> :p2cwrite: 172 :env: None :c2pwrite: 174 :errpipe_write: 176 :creationflags: 0 :preexec_fn: None :universal_newlines: False
Created attachment 679866 [details] File: executable
Created attachment 679868 [details] File: environ
Created attachment 679870 [details] File: dso_list
Created attachment 679872 [details] File: smolt_data
Created attachment 679873 [details] File: core_backtrace
Well, this seems pretty much like what the error says: OSError: [Errno 12] Cannot allocate memory you've run out of memory. Your system seems to have 1GB RAM, but that should be fine - all of my testing is done on VMs with 768MB RAM. So it's got to be something specific to your environment. I'll see if I can identify anything that could cause excess memory use but since I can't reproduce the problem I can't really offer any suggestions or fixes other than "free up some memory and try again". What else was running when you encountered this? I see KDE at least, but I don't know what else was going on... can you try re-running it with fewer things open?
Will, I just met bug 894623 with mock. Although it was with mock, different kernel etc, it might be relevant ...
(In reply to comment #7) > I just met bug 894623 with mock. Although it was with mock, different kernel > etc, it might be relevant ... Nope, totally unrelated. We're not using the "unshare()" system call.
*** Bug 912998 has been marked as a duplicate of this bug. ***
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.