Forum Discussion
File Size causing save issues
Hi Everyone,
I am currently having a problem saving my work. I was getting a message about system memory being too low to save and would close all other applications and save fine.
Now I get the message 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt'. Again closing everything else and then saving works. Although storyline crashes straight afterwards.
I have replaced my RAM (well work did) but I am also wondering about the file size of Storyline projects. I have noticed file size can fluctuate and have read other posts here on it but didn't see an answer as to why this is. I am saving locally but can see a jump of about 20MB without actually making a change to the file.
Recently I wanted to keep some work I did in a training module as a template for future modules. The training module ended up saving at 89,000kb after I deleted all unecessary bits and unused recordings. I then saved the file under a new name and deleted all but the one scene I wanted as a template and it saved as 115,000kb. I can't imagine how this is possible as it is only a fraction of the original file.
I have also noticed that Storyline can use seemingly disproportionate amount of system memory (maybe causing my save problem) my 89,000kb file size project was running at over 700,000kb in system memory at one stage and is now at 362,000kb - at idle as I am obviously not currently telling it to do anything. These numbers, even at idle seem high.
Can anyone explain to me why the save file size of Storyline files can be so random?
20 Replies
Hi James,
Without being able to launch into the exact technical reasons why this happens, we have determined that the file size won't shrink until the project is published. I believe this will be handled better in Update 2, due out soon.
i have used a program called ntcore that converts the 32 bit exe to allow it to take advantage of 4 gigs of ram. i am sure this is in no way support by articulate by it has worked amazing. before the program always crashed when it hit 900 mb ram. i have had it hit as high as 1.8 gigs usage without crashing (yet).
keep in mind, this will only work if you have x64 windows.
Tom
Hi! I am having the same issue. I was wondering where did you put the ntcore file? And did you unzip it? Thank you so much!!!
Thanks Tom and Peter,
@ Peter - from what you are saying it sounds like the file isn't really 115,000kb it just thinks it is. I am looking forward to update 2 and have my fingers, toes and eyes crossed hoping it gives more control of the player buttons.
Peter do you think that this update where it will show the true file size will help with how resource hungry Storyline gets? I frequently make training that is around 900mb in size and the increasing amount of crashing as the file gets bigger is problematic.
In the meantime I will periodically publish projects, which with the unused screens captures deleted will hopefully keep them under 900mb for longer.
@ Tom - I thought Storyline, unlike Studio could be put on a 64bit machine? I was considering putting it on my home computer which is 64 bit so I guess when I do I will need the software you mentioned.
Unfortunately I enquired about a new work laptop (64 bit) but apparently our network settings make that not an option.
James Brandwood said:
@ Tom - I thought Storyline, unlike Studio could be put on a 64bit machine? I was considering putting it on my home computer which is 64 bit so I guess when I do I will need the software you mentioned.
Unfortunately I enquired about a new work laptop (64 bit) but apparently our network settings make that not an option.
Storyline works perfect on a 64 bit machine as is, it just doesnt take advantage of it. The ntcore patch allows a program to come closer to taking advantage of 64 bit by allowing the app to run with a higher memory limit.Tom
Good to know - Thanks Tom.
I have also experienced less crashing after publishing my current poject. The file size stayed around 100,000kb (losing about 15,000kb) but I had no issues saving and only a few cashes while running or returning from a preview.
Same issue, its pretty annoying, please fix
Yo Ahzzma said:
Same issue, its pretty annoying, please fix
Did you try the ntcore patch i mentioned? I know other people have had success with it, as long as you are using 64 bit windows.Tom
Hi Yo,
I am getting a lot of success publishing my work often. I am guessing but it seems to me like it works almost like a 'defrag' and makes it easier for Storyline to keep track of the file when it gets bigger.
Where do i get the ntcore patch
