Forum Discussion
Any clues as to constant refusals to save due to memory issues?
I wanted to share an update on this issue, which I had attributed to a new work laptop that was 64 bit. Articulate and the story file in question I was encountering issues with had worked fine on my previous work issued laptop
After working extensively with me through a support ticket, the Articulate Service Desk identified the culprit as a custom font that wasn't supported by my computer. I'm not even sure where the font came from - I imagine at some stage I downloaded a template from the community and it was in it. When I opened my story file a warning message would pop up indicating that the font wasn't supported, but I had gotten into the habit of just clicking "ok" and moving on with my work. On my old computer this never presented any issues, so I didn't suspect it as a cause on my new computer. However, on the recommendation of the Articulate service desk I rooted out and replaced all instances of the custom font (using instructions at end of this post) and immediately my performance issues improved.
Over the course of 2 weeks working extensively with this large project I had maybe 2 memory related crashes - not ideal, but a HUGE improvement to the dozens daily I was seeing before I removed the custom font packages.
I don't understand why the fonts caused such an issue, but suffice to say, I was delighted to get to the bottom of it. Many thanks to the Articulate service desk who I had a lot of correspondence with on my issues.
How to replace fonts: