Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 2 FirstFirst 12
Results 16 to 18 of 18

Thread: gz_open: fork: Cannot allocate memory - when installing ipk's

  1. #16

    Title
    Forum Supporter
    Donated Member
    Join Date
    Dec 2011
    Posts
    80
    Thanks
    33
    Thanked 6 Times in 6 Posts
    Does this mean the enigma2 is hogging memory?
    Code:
     PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
     1421  1416 root     S     103m 100%   7% /usr/bin/enigma2
     1465  1463 root     R     2980   3%   0% top
     1462   334 root     S     2984   3%   0% telnetd
      105     2 root     SW       0   0%   0% [sched_high]
        6     2 root     SW       0   0%   0% [rcu_kthread]
     1362     1 root     S    13016  12%   0% /usr/softcams/CCcam.2.3.0
      346     1 avahi    S     3692   3%   0% avahi-daemon: running [vusolo.local]
      347   346 avahi    S     3692   3%   0% avahi-daemon: chroot helper
      323     1 messageb S     3048   3%   0% /usr/bin/dbus-daemon --system
      334     1 root     S     3032   3%   0% /usr/sbin/inetd
      749   334 root     S     2984   3%   0% telnetd
      750   749 root     S     2980   3%   0% -sh
     1463  1462 root     S     2980   3%   0% -sh
      327     1 root     S     2664   3%   0% /usr/sbin/dropbear -r /etc/dropbear/dr
      339     1 root     S     2656   2%   0% /sbin/klogd -n
      337     1 root     S     2656   2%   0% /sbin/syslogd -n -O /var/log/messages
     1416     1 root     S     2656   2%   0% {enigma2.sh} /bin/sh /usr/bin/enigma2.
        1     0 root     S     1916   2%   0% init [3]
      306     2 root     SW       0   0%   0% [cifsd]

  2. #17

    Title
    ViX Beta Tester
    Join Date
    Jan 2011
    Posts
    14,099
    Thanks
    3,389
    Thanked 4,102 Times in 3,198 Posts
    from my own experience, enigma2 does hog memory, mainly due to plugins.
    saying that, the solo does work perfectly for me on a default image install.
    I've had one running for months without a reboot.
    When you add extra EPG sources it can struggle but a reboot/flash usually fixes any issue.

  3. #18

    Title
    Forum Supporter
    Donated Member
    Join Date
    Dec 2011
    Posts
    80
    Thanks
    33
    Thanked 6 Times in 6 Posts
    Quote Originally Posted by judge View Post
    from my own experience, enigma2 does hog memory, mainly due to plugins.
    saying that, the solo does work perfectly for me on a default image install.
    I've had one running for months without a reboot.
    When you add extra EPG sources it can struggle but a reboot/flash usually fixes any issue.
    I'm at a loss, all I have installed now is EPG with 1 source and its set to default settings other than that. Also CCcam and some picons. All is working but I cant install any more plug ub unless I enable swap :-\ sounds like some fault. I might redownload the image tomorrow and reflash.

  4. #19
    Larry-G's Avatar
    Title
    V.I.P
    Donated Member
    Join Date
    May 2010
    Posts
    32,542
    Thanks
    7,824
    Thanked 22,937 Times in 12,378 Posts
    Quote Originally Posted by dave_uk View Post
    I just disabled the swap and the box froze as soon I went to plugings/feeds, I SSH'd and tried to execute "free" to check the memory but:
    Code:
    root@vusolo:~# free
    -sh: can't fork
    root@vusolo:~#
    I have installed more Picons, TSPanel, and the football plugin. Only thing I had installed when I got the forking issue's were cccam 2.3.0 and pre packaged apps, I actually remove image player, imdb and media scanner
    Could it be a faulty box ? I didnt get it from WOS as they were out of stock when I wanted one. I got it from ********* who are as reputable. I'm tempted to try Blackhole image but I shouldnt need to, I know VIX should work.

    Thanks
    Dave
    Unlike a lot of other teams who just throw plugins in to the image, most of our included plugins are coded specifically into the image and removing them can it self cause problems, as to memory usage, Linux always uses as much memory as possible as it considers free memory as wasted memory.

    try a fresh flash, but dont remove any of the preexisting included plugins, then set up the box one step at a time to see where its going wrong.
    My posts contain my own personal thoughts and opinions, they do not represent those of any organisation or group but my own.

    If you don't like what I post, Don't read it.

    SIMPLES.

  5. The Following User Says Thank You to Larry-G For This Useful Post:

    dave_uk (09-12-12)

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.