Theofanis Despoudis

Looking at the repo containing the bug It seems that the code triggers the loop originates from this component: https://github.com/mediashane/graphql-bug/blob/2b1a20dab7214377d56e7e163708d4a88e43a01c/src/koa-framework/AcfModules/AcfModules.tsx#L13-L23 It then triggers something and goes back to the same...

I also suspect that because it uses queries from the previous page, it triggers an effect like this: 1. A page is loaded. GQty triggers a schedule to request a...

The code also seems to loop around this block: https://github.com/gqty-dev/gqty/blob/237fb26cabeab75ddb4475b671b6490faa5de1d5/packages/react/src/common.ts#L106-L142

Looking at the code here it looks like it falls into the troublesome case of data-selections-conditionals: https://gqty.dev/docs/react/troubleshooting#data-selections--conditionals The `AcfModules` component is basically the `map` part of the example. I've rewriten...

I also managed to replicated it more consistently. It looks like in the switch statement here: https://github.com/mediashane/graphql-bug/blob/main/src/helpers/renderComponent.tsx Any component that shares the same properties with a different component in a...

Cool

No worries

Sure go ahead. Try to get a few extra hints from this guide here: https://github.com/golang/go/wiki/Performance For example: heap allocations and unnecessary escapes Garbage collection

@theodesp Any luck with any benchmarks?

Not yet but if you write them then all the better!