-
Notifications
You must be signed in to change notification settings - Fork 600
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
SystemStackError: stack level too deep upgrading v7.2.0 => v8.13.1 #1647
Comments
Hi @diclophis! I'm sorry to hear you're encountering an error while trying to upgrade the agent. Thanks for sharing the stack trace. It looks like the error is related to Have you reviewed the 8.x migration guide section on add_method_tracer? Do these changes impact your application's |
I have updated the integration with |
Thanks for trying out the 8.x migration guide! In your |
@diclophis, it would also be helpful if you could provide a gist or other code-based reproduction of the problem. |
@kaylareopelle we do not have any specific setting activated in our We make use of |
We have determined that within the failing controller spec we call through a module implemented essentially as...
The term "Obfuscated" is just placeholder for our actual class/method-names ... |
I think the issue might be an interaction between |
Hi @diclophis, Your given "Expected Behavior" made me smile, and seems completely reasonable. 😄 Thank you for providing us with the obfuscated example code and pointer to the additional information we'd like to have
one thing to try - revert individual files back to their v7.2.0 stateWhen I look at the v7.2.0 versions of tracer.rb, segment.rb, abstract_segment.rb and guid_generator.rb files that are all involved in your provided stack trace, the most significant v8.x agent alterations appear to have been made to another thing to tryOne additional thing to try temporarily just to help narrow down when the issue was introduced would be to test with other
Thanks very much for your patience on this one. A tremendous amount of work has gone into the agent between v7.2.0 and v8.13.1 in the hopes of delivering a better, richer experience for our users and we're sorry you're running into this issue. |
@fallwith please give me a smidge more time, I should be able to make a repo dedicated to reproducing this error. |
Hi @diclophis, just checking in. If you've determined any more information about this one or have anything additional you would like for us to try or look into, please let me know! |
Hi @diclophis. We're going to close this one for now. As soon as you're ready for additional repro steps or debugging, we'll be happy to help! |
Description
During our test suite run, we are encountering an infinite loop leading to a ruby
stack level too deep
Expected Behavior
The newrelic gem to not cause an infinite loop
Troubleshooting or NR Diag results
Steps to Reproduce
We are able to reproduce this error consistently by using the upgraded gem in our test builds
Your Environment
ruby2.7 + rails5.2 + linux
Additional context
possibly related to:
#1590
#731
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):
The text was updated successfully, but these errors were encountered: