Forum Discussion
Serious Lag and Memory Buildup in Long Storyline360 Course – Suspected Media Unloading Issue
Has anyone found a solution to this issue yet? We're facing the same problem across multiple courses. In our case, the lag becomes noticeable when the course is left running for more than 30 minutes—which isn't really that long. The audio finishes playing, but the seek bar continues to lag behind significantly.
The SCORM package is optimized to around 150 MB, and the course contains approximately 80 slides. Despite this, the performance degradation over time is quite severe.
This is becoming a major concern, and unfortunately, we haven't been able to resolve it or even offer a reasonable explanation to stakeholders. Any insights or fixes would be greatly appreciated.
Why “lag” means different things in Storyline
There are a number of discussions here in which people say their course is “lagging,” but they are often talking about very different things. It helps to separate them into three categories:
- Slow screen loads / navigation delays
- Example: clicking Next takes several seconds before the slide appears.
- Usually related to file size, media preloading, or memory bloat.
- Timeline desynchronization
- Example: the narration plays fine, but Storyline’s timeline (seek bar, animations, triggers) starts running behind.
- Audio and visuals drift apart over time.
- Video/audio sync drift
- Example: lips don’t match speech in a video.
- Typically an encoding or streaming issue.
Which one applies here?
From what you describe — “the audio finishes playing, but the seek bar lags significantly, especially after 30 minutes” — this is timeline desynchronization (2).
It’s not about slide loading or video playback. It’s specifically the Storyline timeline struggling to keep up during long runtimes.
Why this happens:
OrvinCastanha 's original hypthesis is on the right track: Storyline does not aggressively unload assets once they’re in memory. Instead, it tends to cache everything the learner has already visited. That leads to:
- Memory bloat from accumulated images/audio.
- Laggy transitions and slower interactions as the session goes on.
- Worse drift when slides have many layers, long audio clips, or embedded video.
- Extra strain if you try to preload media (you’re right to stop doing this).
Unfortunately, there’s no way within Storyline to force a “memory clear” between slides or scenes. Once a course is running in the browser, only a tab refresh resets memory.
What you can do
- Break the course into smaller modules. 80 slides / 150 MB in a single SCORM is on the heavy side; splitting into 20–30 minute topics dramatically reduces drift.
- Chunk audio and sync to audio completion. Instead of one long timeline, use shorter narration files and trigger layers/animations off “media completes.” This masks drift because each chunk realigns timing.
- Reduce slide complexity. Avoid very long timelines with multiple layered interactions. Fewer layers = fewer objects left in memory.
- Test across browsers. Chrome is often worst at memory management; Edge or Firefox may perform better.
- Avoid unnecessary preloading. It frontloads memory use and accelerates bloat.
Bottom line
What you’re running into is a known limitation: Storyline’s browser-based player holds onto assets rather than releasing them. The visible symptom is timeline drift after 20–30 minutes.
I'm not aware of a silver-bullet fix, but design strategies (smaller modules, shorter audio chunks, simpler slides) can mitigate it and keep performance at a level stakeholders can accept.
Thanks for detailed explaination.
in past few years we have created even longer and heavier (in scorm package size) courses in Articulate SL 3 and 360. we never faced this type of issue with timeline desynchronization (2). yes we faced the loading time issues due to the network quality but not this type of syncing issues.This is recent days issue. may be the Tech team can check what happend wrong in past few updates of SL.
Thanks for sharing that perspective — it’s really useful context.
You’re absolutely right: in earlier versions of Storyline (SL3 and the early releases of 360), many of us were building very large, media-heavy courses without seeing the kind of timeline desynchronization (audio finishing but the timeline lagging behind) that people are reporting more often now. Back then, the main complaints were about loading delays (especially over slower networks), not the actual drift between narration and the timeline.
That makes your point an important one: if this is a more recent symptom, it may not just be “inevitable browser memory bloat” but could also reflect changes introduced in recent Storyline updates (e.g., how assets are cached or how the player handles long-running sessions).
I agree it’s worth raising this with Articulate’s tech team directly. If something in the more recent player builds has altered memory handling or asset unloading, that could explain why people are suddenly noticing a problem that didn’t exist in older projects.
In the meantime, the suggested workarounds (shorter modules, chunked audio, simpler slide design) can help mitigate the symptoms — but I think your observation strengthens the case for Articulate to review what might have changed “under the hood” in the last few versions.
