-
Notifications
You must be signed in to change notification settings - Fork 127
Limitations and known problems
Mike Tunnicliffe edited this page Apr 8, 2016
·
7 revisions
appmetrics-1.0.7
:
- Installing from github using
npm install
fails to install correctly leading to "Failed to open library /.../libagentcore.so:/.../libagentcore.so: cannot open shared object file: No such file or directory" (see this issue: https://github.com/RuntimeTools/appmetrics/issues/159) - Installing from npmjs.com using
npm install
does not work from behind a proxy despite the "Change History" advertising that it does.
appmetrics-1.0.6
onwards:
- With early versions of the socket-io npm module, you will get this error https://github.com/RuntimeTools/appmetrics/issues/135 You need to be on a minimum level of socket-io of 1.0.1
appmetrics-1.0.3
onwards:
- On Node.js v4 (before v4.4.0) the process may occasionally crash on shutdown on the V8 ProfilerEventsProcessor thread if profiling is enabled due to a V8 bug (see this commit for more information: https://github.com/v8/v8/commit/8d00c2ca40459d46f127c8156c5afb7bfa79d9e6).
appmetrics-1.0.1
through appmetrics-1.0.3
:
- Mac OS X system CPU usage is not collected, will read 0
- Under some circumstances with io.js v2.5 on Mac OS X there is a warning printed and the command line is not collected, will read as blank