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

Error: C stack usage [large number] is too close to the limit #11

Open
M-Jen98 opened this issue Mar 16, 2023 · 0 comments
Open

Error: C stack usage [large number] is too close to the limit #11

M-Jen98 opened this issue Mar 16, 2023 · 0 comments

Comments

@M-Jen98
Copy link

M-Jen98 commented Mar 16, 2023

Hello,
I am trying to use the SentimentAnalysis package to analyze a collection of TripAdvisor reviews for research. I have a dataset of 178 reviews in a single variable column assigned as SA. Then tried to run this command:

sentiment <- analyzeSentiment(SA)

Which prompted the error

Error: C stack usage 7977028 is too close to the limit

I tried using the direct example from the documentation
analyzeSentiment( SA, language = "english", aggregate = NULL, rules = defaultSentimentRules(), removeStopwords = TRUE, stemming = TRUE )

Which led to a similar error

Error: C stack usage 7976404 is too close to the limit

I have been using R Studio Cloud (aka Posit Cloud) for this research but I attempted the exact same code in the desktop RStudio version and encountered this error instead:

Error: node stack overflow
Error during wrapup: node stack overflow
Error: no more error handlers available (recursive errors?); invoking 'abort' restart

Some initial Googling of the issue makes it seem like it is an issue with recursive code but I do not think that would be the case here. Another thing I cannot make sense of is that I tried this exact same code with nearly the exact same data perhaps 6 months ago and it worked perfectly. Since then I have added less than 10 new reviews to the data (going from 170 to 178). Could that minor increase really cause this issue? If so, what would be a workaround for analyzing all 178 reviews properly? I would appreciate any suggestions for fixing this problem.
Thank you

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

No branches or pull requests

1 participant