Skip to main content
J
JK_1074468213-Aquamarine
13-Aquamarine
July 28, 2025
Solved

Thingworx Mashup Crash After Open for a Long Period of Time

  • July 28, 2025
  • 3 replies
  • 1154 views

Hi all,

 

My team has a mashup that is essentially a dashboard that is kept open in our plants for long periods of time without refresh. Specific details of the mashup aren't important for the issue we are seeing. After being open for longer periods of time, the mashup will crash with this error:

JK_10744682_0-1753723149025.png

 

Has anyone encountered this before or know of any way to prevent this from happening? We would like these dashboards to be open during the shifts on monitors in the plant without having to refresh due to a random crash after being open for a while. Any input is greatly appreciated!

 

Best answer by VladimirRosu_116627

Hi @JK_10744682 

Wouldn't an AutoRefresh with a target of 8 hours that would trigger an Expression with TW.location.reload() effectively solve this?

I'm looking at this from the perspective of time invested in finding out the root cause (which is theoretically the correct path) versus just time invested in this option.

 

3 replies

V
VladimirRosu_11662719-TanzaniteAnswer
19-Tanzanite
July 28, 2025

Hi @JK_10744682 

Wouldn't an AutoRefresh with a target of 8 hours that would trigger an Expression with TW.location.reload() effectively solve this?

I'm looking at this from the perspective of time invested in finding out the root cause (which is theoretically the correct path) versus just time invested in this option.

 

    Rocko
    Rocko19-Tanzanite
    19-Tanzanite
    August 14, 2025

    Interesting. I would have expected after 8 hours the browser session is expired and you'd have to re-login.

    C
    Constantine18-Opal
    18-Opal
    August 14, 2025
    I would guess they are calling services on timer, and Mashup Runtime logs is what leaks memory.
    Rocko
    Rocko19-Tanzanite
    19-Tanzanite
    July 29, 2025

    I would check the console logs. The error says Out of memory, so you need to find out what is eating your memory. It might be a widget with memory leak. Developer Tools (F12) can help finding this.

    Having an auto-reload might help, I would use a frequency below session-timeout (30min by default).

    C
    CharlesJi16-Pearl
    16-Pearl
    August 14, 2025

    Hi @JK_10744682 

    It appears that there is a reply that answers your question.  For the benefit of other Community Members who may have the same question, it would be great if you could designate it as the Accepted Solution.

    In the event that this response did not answer your question, please post your current status so that we can continue to support.

    Thanks for using the PTC Community!

    Regards,

    Charles

    Terms & ConditionsCookie settingsAccessibility statement