XOJO CLEAR STRING ARRAY VERIFICATION

That showed a ton of dictionaries containing JavaScript snippets, probably stuff Xojo's web engine sent to the browser. For my test code I added code to dump those dictionaries to a text file. I wondered why we had so many dictionaries.

But when I let first session expire and then create 3 new ones and wait for those to close, the counts should go back to normal. Not for the first session as it initializes a couple of global objects.

At least I would expect that when a session ends, we go back to the object counts we had before. The print showed that with newer Xojo versions the EEWeb project leaks thousands of dictionaries. Just counts on how many arrays of each type (integer, object, boolean, etc.) and what object classes via Introspection like how many Dictionaries, JSONItems, WebPages, etc. The code uses runtime object iterator to loop over all objects and counts how many of each class/vartype we have. Now the hunt continues because while looking for the bug we got a little code to dump class counts.

XOJO CLEAR STRING ARRAY VERIFICATION

And that one was fixed in April, so it may be in current test version and may go into verification and the next release. This bug turned out to be a duplicate of 63378. By reproducing it with the official EEWeb sample project, it was clear that it's not my own code. The suspicion was that somewhere in the web framework may be a weak reference. Hunting a memory leak in Xojo Web target A few months ago we saw memory leaks in the Xojo web engine.

Xojo clear string array