Perspective Memory Leak, pages not shutting down when tab closed

[Jay_Baker]

I've got a memory leak issue in Ignition, where Ignition keeps a page running after you close the browser tab. This affects memory and processor on both the client and server, as (in this case) I've got data updating on a timer, so updates continue to happen indefinitely, as far as I can tell.

I've made a simplified example - essentially, a test view which just has a custom parameter bound to a five second timer, printing out the page id to the logs. This shows that the page remains running when the browser tab is closed.

If I then open the page again in another tab, a second page id starts printing to the log, and so on, for as many times as I do this, until my computer starts to melt. In this shot, I have now Perspective tabs left open, and yet...

Note - pages DO seem to close correctly (and trigger the onShutdown event) if I navigate to another Perspective page instead of closing the tab.

So - am I doing something wrong here? Is there any way for these pages to detect that they are orphaned, and force themselves to shutdown?

Ignition v8.1.33. Browser, recent versions of both Chrome and Edge.

[Jay_Baker]

Update: this seems to happen even with pages with no timers, or refresh code, etc.

I've been logging the number of active pages in the session (sourced from system.perspective.getSessionInfo()), and once a page is created, it doesn't seem to go away until I manually kill the session (or, until the Trial Mode on my dev box times out after two hours).

I've also checked this on our production server - I opened a page in a new tab and then immeditately closed it, then repeated this a few times - and they never seem to close. The session is still there an hour later, with all the pages still active.

[Iggy_the_dog]

With the shutdown being called the session should be closing. I am curious if this occurs in the most recent version of Ignition? Also do you have a screenshot of the status>performance page?