Skip to content

Hage Yaapa
hacksparrow

Organizations

@IBM @strongloop @expressjs @jshttp @pillarjs @Tanilogy
May 24, 2016
@hacksparrow

I will working on this and other open issue in the 1st week of June.

May 24, 2016
hacksparrow commented on pull request expressjs/express#2900
@hacksparrow

@demoneaux, which older versions of V8/Node are affected? @dougwilson I am in favor of option 1, with a comment that it has been merged on a branch…

May 24, 2016
hacksparrow commented on pull request expressjs/express#2722
@hacksparrow

Great. StandardJS should take care of such issues.

May 24, 2016
hacksparrow commented on pull request expressjs/express#2722
@hacksparrow

@dougwilson past stance on these types of pull requests (even when I was still with other contributors) was not to accept them, as they don't par…

May 23, 2016
@hacksparrow
Possible memory leak in v4 on node v6
May 23, 2016
@hacksparrow
  • @hacksparrow 8248a5c
    support current node versions only
May 23, 2016
May 23, 2016
@hacksparrow
May 23, 2016
@hacksparrow
May 23, 2016
@hacksparrow
May 23, 2016
@hacksparrow
May 23, 2016
hacksparrow merged pull request hacksparrow/safe-eval#2
@hacksparrow
Added opts arg to pass to vm.runInNewContext
1 commit with 2 additions and 2 deletions
May 23, 2016
@hacksparrow
Include information about the reference to the app object in the request and response objects
May 23, 2016
@hacksparrow

Fixed by 8de3401

May 23, 2016
@hacksparrow
  • @hacksparrow 8de3401
    add reference to app object from req and res
May 23, 2016
@hacksparrow

@raeesaacapita which version of Node and what OS?

May 23, 2016
@hacksparrow
Include information about the reference to the app object in the request and response objects
May 21, 2016
@hacksparrow

+1 for standardjs.

May 20, 2016
hacksparrow commented on issue expressjs/express#2997
@hacksparrow

It indeed seems to be because of the Error objects holding the stack frames. @dougwilson @lykkin maybe we can close this now?

May 20, 2016
hacksparrow commented on issue expressjs/express#2997
@hacksparrow

So --stack_trace_limit=0 stops the RAM consumption from ballooning.

May 20, 2016
@hacksparrow

That means the generator is not installed or not installed properly. Try running npm install express-generator -g again and see what you get. Make …

May 20, 2016
@hacksparrow
cant generate express app
May 20, 2016
@hacksparrow

@nasr18 npm install express-generator -g is for installing the generator. To generate an sample app run express yolo, where "yolo" would be the nam…

May 20, 2016
hacksparrow commented on issue expressjs/express#2997
@hacksparrow

@dougwilson nothing yet, let me add --stack_trace_limit=0 and see if it makes any difference.

May 18, 2016
@hacksparrow

Guys, I got disconnected due to a bad network. And it doesn't seem to be improving.

May 18, 2016
@hacksparrow

yes

May 18, 2016
@hacksparrow

Waiting for the link.

May 18, 2016
May 18, 2016
hacksparrow commented on issue expressjs/express#2997
@hacksparrow

gobench made all the difference. I can now observe the RAM consumption growing drastically and CPU usage shooting up to 100% too. We will look fur…

Something went wrong with that request. Please try again.