So just to eliminate the off variable I updated my snapshot. Updated packages,
etc, etc
And now node works fine...
Ken
On Wed, Jun 06, 2018 at 09:28:39PM -0400, Ken M wrote:
> On Wed, Jun 06, 2018 at 09:10:59PM -0400, Thomas Frohwein wrote:
> >
> > I run ksh. Doubt that bash is the cause though
On Wed, Jun 06, 2018 at 09:10:59PM -0400, Thomas Frohwein wrote:
>
> I run ksh. Doubt that bash is the cause though...
> Might wanna check if you have the same problem with ksh.
>
I tried in sh before submitting and got the same problem, I just tried ksh and
the same. Sorry for omitting that I t
I can't reproduce this on -current amd64, neither with a snapshot from last
week, nor after updating today.
thfr@e5570:~$ node -v
v8.11.1
thfr@e5570:~$ node
> console.log('test log');
test log
undefined
> .exit
thfr@e5570:~$
> node -v
> bash: /usr/local/bin/node: Ca
The subject is the problem:
node -v
bash: /usr/local/bin/node: Cannot allocate memory
I am on current, last grabbed the snapshot last Friday I think.
Plenty of swap and memory available
vmstat
procsmemory pagedisk traps cpu
r s avm fre flt re
4 matches
Mail list logo