Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum call stack size exceeded on pubsub Events #2954

Closed
timestep opened this issue May 20, 2015 · 5 comments
Closed

Maximum call stack size exceeded on pubsub Events #2954

timestep opened this issue May 20, 2015 · 5 comments

Comments

@timestep
Copy link
Contributor

Hello all,

I would like to add that I'm encountering an identical issue to:
#2636

Also possibly related are
#2813
https://github.com/balderdashy/waterline/issues/891

/Users/kevin/Documents/dayPack/node_modules/sails/node_modules/lodash/dist/lodash.js:2415
    function isObject(value) {
                     ^
RangeError: Maximum call stack size exceeded

This occurs immediately after any attempt to use any pubsub method on the server or .message() event.

According to this commit,e4f2a26 ,it is supposed to be fixed...

Sails v0.11.0
"sails": "0.11.0",
"socket.io-redis": "^0.1.4",

I can provide additional information if needed.
Any suggestions or possible solutions or oversights I have made please let me know.

I am opening this ticket since there are not any particularly clear solutions to this issue nor issues that doesnt involve using _.clone or _.cloneDeep and seems to have been fixed in the master branch... However I just updated my sails version recently to v0.11.0.

@sgress454
Copy link
Member

Fixed by #2865? @particlebanana?

@Oldwo1f
Copy link

Oldwo1f commented Jun 2, 2015

+1

@scott-wyatt
Copy link

Seems this is still an issue with a fresh sails install up to 0.11.1, perhaps an npm patch is needed?

@gunish
Copy link

gunish commented Aug 12, 2015

Any workarounds for this ?

@sailsbot
Copy link

Thanks for posting, @timestep. I'm a repo bot-- nice to meet you!

It has been 30 days since there have been any updates or new comments on this page. If this issue has been resolved, feel free to disregard the rest of this message. On the other hand, if you are still waiting on a patch, please:

  • review our contribution guide to make sure this submission meets our criteria (only verified bugs with documented features, please; no questions, commentary, or bug reports about undocumented features or unofficial plugins)
  • create a new issue with the latest information, including updated version details with error messages, failing tests, and a link back to the original issue. This allows GitHub to automatically create a back-reference for future visitors arriving from search engines.

Thanks so much for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants