Hi, I'm getting a SyntaxError crash when running vtop, the error message is as follows:

evalmachine.<anonymous>:2
[email protected] | MIT | deps: 10 | versions: 47
^

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:74:7)
    at createScript (vm.js:246:10)
    at Object.runInNewContext (vm.js:291:10)
    at safeEval (/usr/lib/node_modules/vtop/node_modules/safe-eval/index.js:13:6)
    at /usr/lib/node_modules/vtop/upgrade.js:25:24
    at ChildProcess.exithandler (child_process.js:273:7)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:947:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:236:5)

Instead of telling people to use sudo under "How to install", we should rather tell them to fix their npm permissions instead.

Globally installing npm packages using sudo is not considered a good practise. 😊

As soon as I start moving my mouse, vtop quits (probably crashes) and I start to see what looks like the mouse coordinates in ASCII in the terminal input. It sometimes comes back to normal after a few moments, others I have to run reset. This happens on both terminator and xfce4-terminal. I haven't tried anything else.

One of my programs consumes a massive amount of memory. For some reason, this gets reported as "NaN". Furthermore, the leading process character get chopped off of the process name.

Detect "Real" memory usage on a mac, acts more like activity monitor.

Honestly the code needs cleaning but I have not seen anyone else attempt this, This is what I have been using for a bit.

The os-utils module reports erroneous used memory percentage, in particular, it considers memory used by the kernel's disk caching subsystem as used memory, when it should in reality be considered free as it is transparently let go when memory is low. See http://linuxatemyram.com.

This changeset fixes this by detecting if we're on Linux, and if so, runs free -m in a child process and screenscrapes its output. os-utils does provide a .freeCommand() function which is supposed to be doing this, but it also returns erroneous numbers.

Before: After:

(shown with gnome-system-monitor on the side for comparison)

This pertains to vtop not launching and instead returning to shell without a peep.

Thank you very much for helping out. I'm more a n00b than I would like to be so I appreciate the patience.

$nodejs -v
v0.10.25

$lsb_release -a
No LSB modules are available.
Distributer ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty

Per your request, 'export' output below:

ptdecker@ptdecker-Satellite-L55-A:~$ export declare -x CLUTTER_IM_MODULE="xim" declare -x COLORTERM="gnome-terminal" declare -x COMPIZ_BIN_PATH="/usr/bin/" declare -x COMPIZ_CONFIG_PROFILE="ubuntu" declare -x COMP_WORDBREAKS="
"'><;|&(:" declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-JexEHW5ZRs" declare -x DEFAULTS_PATH="/usr/share/gconf/ubuntu.default.path" declare -x DESKTOP_SESSION="ubuntu" declare -x DISPLAY=":0" declare -x GDMSESSION="ubuntu" declare -x GDM_LANG="en_US" declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated" declare -x GNOME_KEYRING_CONTROL="/run/user/1000/keyring-Y34XBy" declare -x GNOME_KEYRING_PID="1779" declare -x GPG_AGENT_INFO="/run/user/1000/keyring-Y34XBy/gpg:0:1" declare -x GTK_IM_MODULE="ibus" declare -x GTK_MODULES="overlay-scrollbar:unity-gtk-module" declare -x HOME="/home/ptdecker" declare -x IM_CONFIG_PHASE="1" declare -x INSTANCE="" declare -x JOB="dbus" declare -x LANG="en_US.UTF-8" declare -x LANGUAGE="en_US" declare -x LESSCLOSE="/usr/bin/lesspipe %s %s" declare -x LESSOPEN="| /usr/bin/lesspipe %s" declare -x LOGNAME="ptdecker" declare -x LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.oga=00;36:.spx=00;36:.xspf=00;36:" declare -x MANDATORY_PATH="/usr/share/gconf/ubuntu.mandatory.path" declare -x OLDPWD declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" declare -x PWD="/home/ptdecker" declare -x QT4_IM_MODULE="xim" declare -x QT_IM_MODULE="ibus" declare -x QT_QPA_PLATFORMTHEME="appmenu-qt5" declare -x SELINUX_INIT="YES" declare -x SESSION="ubuntu" declare -x SESSIONTYPE="gnome-session" declare -x SESSION_MANAGER="local/ptdecker-Satellite-L55-A:@/tmp/.ICE-unix/1925,unix/ptdecker-Satellite-L55-A:/tmp/.ICE-unix/1925" declare -x SHELL="/bin/bash" declare -x SHLVL="1" declare -x SSH_AGENT_LAUNCHER="upstart" declare -x SSH_AGENT_PID="1860" declare -x SSH_AUTH_SOCK="/run/user/1000/keyring-Y34XBy/ssh" declare -x TERM="xterm" declare -x TEXTDOMAIN="im-config" declare -x TEXTDOMAINDIR="/usr/share/locale/" declare -x UBUNTU_MENUPROXY="1" declare -x UPSTART_SESSION="unix:abstract=/com/ubuntu/upstart-session/1000/1781" declare -x USER="ptdecker" declare -x VTE_VERSION="3409" declare -x WINDOWID="27262987" declare -x XAUTHORITY="/home/ptdecker/.Xauthority" declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg" declare -x XDG_CURRENT_DESKTOP="Unity" declare -x XDG_DATA_DIRS="/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/ptdecker" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_ID="c2" declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0" declare -x XDG_VTNR="7" declare -x XMODIFIERS="@im=ibus"

I've recently found about vtop, and from what I've seen it looked really cool. But after like 1 second of launching, the following error occured:

SyntaxError: Unexpected token ILLEGAL
    at Object.exports.runInNewContext (vm.js:48:16)
    at safeEval (/usr/local/lib/node_modules/vtop/node_modules/safe-eval/index.js:13:6)
    at /usr/local/lib/node_modules/vtop/upgrade.js:25:24
    at ChildProcess.exithandler (child_process.js:191:7)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:862:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)```

hi first, I want to think you for the project, I find it cool :) But I have a little problem, I don't if you too have the same problem, vtop uses processor more than htop, as you can see on the picture, 51% vs 3%

I didn't realize that this commit sort of broke the colors on the table. When I booted it into the dark theme, it looked hideous. Now they look nice and beautiful again.

Note: I'm aware that the commit added necessary fields, but it didn't honestly look like the color scheme was chosen well. No offense intended towards James.

Thanks :)

evalmachine.<anonymous>:2
[email protected] | MIT | deps: 10 | versions: 47
^

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:74:7)
    at createScript (vm.js:246:10)
    at Object.runInNewContext (vm.js:291:10)
    at safeEval (/usr/local/lib/node_modules/vtop/node_modules/safe-eval/index.js:13:6)
    at /usr/local/lib/node_modules/vtop/upgrade.js:25:24
    at ChildProcess.exithandler (child_process.js:273:7)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:957:16)
    at Socket.stream.socket.on (internal/child_process.js:378:11)
    at Socket.emit (events.js:182:13)

I've successfully installed node-0.10.48 and vtop-0.5.7 on a legacy armv7 Linux device. However, when attempting to exec the vtop command I receive a command not found error. After reviewing the vtop wrapper, I'm beginning to believe it's an incompatibility issue with shell (sh). Shell contains the builtin exec command (# type exec), but it doesn't have the builtin command command (# type command). Is this a known compatibility issue? Thank you for your assistance.

@MrRio was hoping you could advise me on using this package as a lib rather than a gui. I wan't to periodically log some CPU stats, which is fairly easy to do (thanks!). I'm just trying to understand the output a little. Here's an example of some:

{
  Command: 'Google Chrome Helper (Renderer)',
  Count: 18,
  'CPU %': '0.8',
  'Memory %': '7.3',
  cpu: 4.5,
  mem: 7.3
}
{
  Command: 'com.apple.WebKit.WebContent',
  Count: 41,
  'CPU %': '3.7',
  'Memory %': '26.9',
  cpu: 22.100000000000005,
  mem: 26.900000000000002
}
{
  Command: 'node',
  Count: 6,
  'CPU %': '1.2',
  'Memory %': '1.6',
  cpu: 7,
  mem: 1.6
}
{
  Command: 'webstorm',
  Count: 1,
  'CPU %': '0.9',
  'Memory %': '8.5',
  cpu: '5.6',
  mem: '8.5'
}

My question is, what's the difference between CPU % and cpu?

From what I searched the answer is no.

But I still need it, I use a custom keyboard and needs to remap hjkl to the correct keys. Is it possible to edit the code maybe and change the keys to the correct ones? It shouldn't be a great change. Searching the code I found where the display text is defined but not where the action is mapped. Help?

I created a Dockerfile which creates an image for vtop and can be accessed at snpranav/vtop. The reason behind doing this was to make vtop more cross-platform. This also lets people use vtop without having to install Node.js on their host machine (All you need is docker).

I have also updated the README with instructions on how to run vtop as a docker container.