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

Stack Overflow on Federated Schema Gateway Service in 13.5.0 #6494

Closed
1 task done
albernhagen opened this issue Aug 30, 2023 · 2 comments · Fixed by #6501
Closed
1 task done

Stack Overflow on Federated Schema Gateway Service in 13.5.0 #6494

albernhagen opened this issue Aug 30, 2023 · 2 comments · Fixed by #6501

Comments

@albernhagen
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Product

Hot Chocolate

Describe the bug

We have a UI that issues a high number of requests to our gateway service, a number of which do queries in parallel to different domain services. After some time (sorry I don't have better numbers), we get a stack overflow error:

Stack overflow.
Repeat 104670 times:
--------------------------------
at System.HashCode.Combine[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Int32, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](System.__Canon, Int32)
at HotChocolate.Path+RootPathSegment.GetHashCode()

Steps to reproduce

I wish I could share our repos but they are private. In general, it is:

  1. Setup a federated schema service with domain services
  2. Issue a high number of client-side concurrent requests to the gateway service of which certain queries include types from both domain services in the same query
  3. It'll eventually fail as noted above.

Relevant log output

Noted in the bug description.

Additional Context?

This happens when upgrading to 13.5.0 but does not happen with 13.4.0.

Version

13.5.0

@michaelstaib
Copy link
Member

Thanks for reporting ... I will have a look at this and think I know why this is happening.

@michaelstaib
Copy link
Member

Its fixed with 13.6.0-preview.4

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

Successfully merging a pull request may close this issue.

2 participants