This same happens with an empty project (web2.0) where some url would be called like http://mydomain.com/test (multiple times)
In app handleurl there is nothing to handle this nor is a webpage or session called ever. It still leaks memory this way. Meaning that it’s probably internally before App.HandleURL and not user code, since none was added.
Here is a FB case about this: <https://xojo.com/issue/63378>