RW5 BETA ISSUES - SHUTDOWNS - BEACH-BALLS
Previous to the Beta (RW5 5.01-5.04), I had been experiencing App shutdowns, beach-balls, operative hangs and numerous other related errors and issues when attempting to export or publish. The best I could experience was 75% completion before whatever flavor of failure would occur. I certainly know much of my problem dealt with a project having over 1.5 MB of data and 3000 files.
Your RW5 BETA actually enabled my very large project to complete without errors. I was most happy with the this new update. Along the way, I have discovered some issues that I learned to work around, but would be nice it they could be fixed?.....
After performing any export or publishing of a project, I must completely shut down RW and reopen in order to work on another project. If I fail to do this, I will experience an immediate App shutdown or typical error as briefed above. This BETA remains solid and functional AS LONG as I continued to shutdown and restart RW for every different project I work on. As I have several projects, this can be a bit time consuming, but I am so appreciative of having a working RW that I will live with this issue if I must. My only hope is this can be addressed, making my life a bit easier.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Luke Hefson on 17 Feb, 2011 10:24 AM
Hi there,
Thanks for the message. I'm sorry to hear that you are having issues with RapidWeaver, I understand what an inconvenience this may be for you.
How large is your RapidWeaver project in total (you mention 1.5MB but perhaps you mean 1.5GB?).
Are you running any third-party plugins in your project and if so are they all up to date?
We're continuing to investigate the way that RapidWeaver handles very large project files and I will certainly pass your comments onto our developers - I'm sure they will be very helpful!
In the meantime, if you have a very large project you might like to consider splitting it up into smaller, more manageable, 'mini-projects'. A great tutorial on this by third-party developers YourHead can be found here:
http://yourhead.tumblr.com/post/91931613/how-to-split-a-large-rapidweaver-site
Please let me know if I can be of any further assistance.
Kind regards,
Luke
-- Luke Hefson
Support & QA, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within two business days.
Luke Hefson closed this discussion on 17 Feb, 2011 10:24 AM.
skypilota72 re-opened this discussion on 17 Feb, 2011 01:19 PM
3 Posted by skypilota72 on 17 Feb, 2011 01:19 PM
Yes - 1.5GB
I have many 3rd party Plugins and Stacks, and all are RW5 compatible and fully up to date.
As I had said in my former text, as long as I reboot RW5 Beta for each new project, there is no problem, and therefore no need to split the project up.
This wasn't the case with RW5 .01-.04 which
Support Staff 4 Posted by Nik Fletcher on 17 Feb, 2011 03:55 PM
Hi there
We've not made any changes to RapidWeaver relating to the memory management of massive projects, and as such the project's size will likely be causing this issue. We're working to improve the support for larger files but I can't comment on when we'll be able to smoothly handle projects of that size.
Please let me know if I can be of any further assistance.
Kind regards,
Nik
-- Nik Fletcher
Support & QA Manager, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within one business day.
Nik Fletcher closed this discussion on 22 Feb, 2011 03:46 PM.