@dwayner Well 100 photos at 5 Mb would still only be 500 Mb. Large indeed, but it doesn’t explain the 2.3 Gb. So I’m going to make some guesses: either you have a camera that creates really big JPGs and you used the originals, OR over time you’ve put several big pictures into RW but you only ended up using about 100 of them.
I have a camera that takes big JPGs that are about 23 Mb. So 100 of those would get you at about 2.3Gb. I doubt this happened to you, but it’s possible.
For many people it would be more likely that they treated RW somewhat like a word processor or PowerPoint where they drag in materials (mainly photos) but then delete several from their slides as they go through the editing process, or they just change their minds. But those old unused photos are still stored in the RW project file (at least as I understand it).
The 2.3 Gb file size on it’s own probably did not cause your problem, but it certainly doesn’t help. It may be a contributing factor.
Probably what you need now is RW project file surgery. And that’s nothing any of us should be guiding you through. I’d contact RW support directly. They’ll probably want you to get them the project file. It’s a huge file, but getting them the original is the only way they can figure things out and hopefully fix the problem.
Is it possible there’s a general bug in RW that creates your problem? Sure. But it’s not a common problem, and I’m focused on that huge file size and the consequences of that are likely contributing factors.
I have no idea how big your website it, but let me give you an example of what warehousing does. I’m currently working on a course website with lots of videos (probably 30 to 40), lots of audio files (easily 100+), and several images. I have about 40 pages total with lots of content. Project file size: 15 Mb. But that’s because I warehouse: videos to Vimeo or YouTube, audio directly FTPed to my hosting account, images directly FTPed to my hosting account or linked to via Flickr.
I’m not trying to say you should do things exactly as I have done. Many people don’t run into problems and they take different approaches. But in the long run, after you’ve sorted out this mess, it is worth your time to learn how to optimize images and how to warehouse your biggest and most important materials (likely your images).
But right now I doubt we can help you, and a deep look by real pros are needed to fix this. I doubt there’s any easy fix to your issue. Even if it got “fixed” for one time the problem would likely reappear sometime again down the road. The good news is I think the RealMac people should be able to sort this out for you but it may take a few days.