Browser Slowness when Model Building

Has anyone else noticed that after 15-30 minutes of model building activity (opening modules, opening lists, updating formulas, opening split views, toggling from blueprint to module view, etc.) that browser tabs slow down and stop responding, and has to be restarted.

Been an issue for a few weeks now.

Hardware and software:

- PC: Lenovo T16

- CPU: 12th Gen Intel(R) Core(TM) i7-1270P 2.20 GHz

- RAM: 32.0 GB (31.7 GB usable)

- Chrome Version 122.0.6261.94 (Official Build) (64-bit)

- Windows 11 Pro Version 22H2

Root cause analysis:

  • Persists between machine restarts
  • Affecting multiple Anaplan tenants, model builders, all using Chrome and Windows
  • Has been happening for a few weeks now
  • Issue is immediately resolved if you **** the browser tab and open a new tab, at which point users can pick back up where they left off without issue

Based on root cause analysis, wondering if there's some sort of memory leak affecting Anaplan on Chrome, but surprised it hasn't been raised yet.

Reaching out here to gauge if this is affecting anyone else, so that we know we're not crazy.

Answers

  • Dikshant
    edited March 1

    Maybe try building a new model and do some basic model building activities. Do you still encounter the same issues? I am also using chrome and not experience any slowness or lags while using Anaplan.

  • Bit late to this, but we have the same issue.

    New tab is fine for a while until it degrades, becomes slow then crashes the tab with the 'aw, snap' message appearing.

    Have come to a similar conclusion around memory not being released.. the session just keeps taking more and more until it hits a limit and crashes.

    Haven't yet identified a route cause, but don't have the same issue using a Mac/Safari.

  • Thanks @luke_e, makes me feel a bit less crazy.

    At some point the issue stopped, but difficult to attribute it to any one thing I did, unfortunately.

    I would try the usual — (1) clearing cookies, (2) update browser to the latest version, (3) disable extensions…all that good stuff.

    The only additional thing I can remember doing around the time it stopped was I disabled all facets of autocomplete in the formula editor. Aside from it being a bit annoying, my thinking was that the only thing somewhat new that would consume member in the modeling experience that I was visiting frequently was the formula editor, and if that memory wasn't released, I could see that accumulating until the tab crashed.

    I can't recall seeing the issue again after I did that. I've since had it turn back on (after a cookie reset), but it seems like the issue hasn't returned.

  • This content has been removed.
  • Thanks @kjacokes - had also observed the formula editor, specifically the autocomplete contributed to slowness and disabling did improve the situation, but still seems to run out of memory if you're consistently making changes (just takes a bit longer to get there). Clearing cookies/cache unfortunately didn't make much of a difference.

    I do find this setting does tend to reset itself when you close/reopen Chrome which isn't ideal (and, i'm not clearing cookies on close). Not sure if you have/had the same behaviour.

    Have asked our ITS to suss out the enterprise proxy to ensure all the Anaplan domains listed below are allowed through, as we previously had issues with filtering.

    Will post back if I find a definite cause.

    Cheers,

    L

  • Can you try turning on crash reporting for me?

    chrome://crashes 

    I’ve just done the same and will post here if it happens to me again. Perhaps we can compare notes so we can send some data points to support.