Forum Discussion
Storyline 3 Error: Available Memory is Low
We are getting this error on a machine that is running Windows 10. It is an HP Z600 workstation, has dual Xeon processors and 32Gb of RAM. Storyline is the only application running. Ev...
I've just discovered this thread after searching for several days for any clue to why storyline 360 has been running so slowly and clunkily (is that a word?) recently. I was thinking that something in the last update or two must have introduced a bug? But in seeing this tip from Alyssa - I found this folder (Win 10 system) C:\Users\User\AppData\Local\Articulate\360
Then deleted all the files inside it - there were over 6000 in there. This immediately restored a good chunk of the missing performance and cured the frustrating latency from the UI.
I can only assume that Storyline was running out of application memory or system resources in some way. Can I recommend to the Storyline dev's that if my hunch is right? (admittedly it's a guess on my part) - that they consider an automated way to purge the contents of system file locations like these....so the app keeps running more smoothly over time.
Regards (And thanks Alyssa if you're still on the team there)
So glad I stumbled upon your reply Peter - I am fighting and losing battle with SL360 - no amount of support cases or reformatting my more than capable PC has helped and I'm getting the same issue over and over and over again.
Fingers crossed your reply will make a difference to my issues too!
Well. I wish you luck. I have since discovered that Storyline re-populates this file location with a couple of thousand folders and several hundred MB of data soon as you create a new storyline project. Seems like this is just part of its normal function so maybe that is not the root of the problem...although when I cleared this folder out. UI performance instantly improved for a while.
Since then I have received some advice after logging a support case. One piece of that was to remove then reinstall SL360. Which I did 2 days ago. This also gave me back some decent UI performance and I thought it was a fix but while working on a project yesterday and creating an object from a series of .jpgs to give me 10 states, I was seeing significant sluggishness in UI response. It feels like the application really is running out of memory or something similar. I had to delete those states and will need to come up with another way to build the interaction I want.
I am using a new (6 month old) powerful computer spec’d out for 3D work so it’s all a bit baffling.
Maybe SL should be built as a 64 bit application? Or maybe that has nothing to do with it, as not everyone is reporting this kind of problem. Let me know how you go?
