iWeb crashes when I publish. I can not publish to a folder, publish all, or publish. It seems to crash around the same place, but I can't say it always crashes when it's on the same item.
I've tried to boot into safe mode and publish, but still no luck.
It's relatively small... 60 or so blogs and about 2 dozen photo pages.
I'm travelling so I don't have access to anyone else's machine to try swapping around the domain file.
I'm cranking on an intel Macbook Core Duo 2 GHZ with a gig of ram and plenty of hard drive space.
Thanks in advance
Macbook Core Duo 2.0,
Mac OS X (10.4.9),
1 GB RAM, 120GB HD
6. To publish (and they suggested this at the apple
store) don't hit publish in the lower left corner of
iWeb, nor Publish All in the menu, because these
republish the WHOLE thing every time and take f o r
e v e r . Instead, choose "publish to .mac". This
wil publish only the new entry, any ones you have
made changes to, as well as the main blog page and
the archive.
Huh. Now that's interesting. I'll do that from now on.
After I purged by blog (zapped about 25 entries), I have had no problems. What's funny is I have built the blog back up beyond 25 entries and I still have no problems. I’ve also added new pages, etc. All I can surmise is I somehow lucked out and zapped that one corrupted entry and/or image. One entry contained an audioclip. Somehow I think that might have been my problem.
Frankly, I don't think the guys at the Genius Bar have a clue. We have proven here it has nothing to do with memory or size, and my best theory about # of blog entries my not be the case after all. I think it's simply one corruption in one image can fry the entire site. That's pretty scary, and I hope it's something they will fix.
I just had the same problem. I do have lots of pics 95 on one page, and have 3 pages that I had planned on putting the same amount. When I was at the apple store for pro-care training a few weeks ago, I asked this question specific if I could load all these pics on my website and they did not see a problem with it. Everytime I go to publish now I get .mac error.
My pics are big so might try making them e-mail size.
iWeb has been crashing on Publish the last couple of days. Thanks to all who have posted possible fixes. I'll give some of them a try tonight. My Domain file is 1.87 GB. I have over 670 jpegs of my photo prints and about 240 blog entries with a jpeg in each. I've always just drug from the finder window list because it's so easy. I haven't had any problems until this--except it takes forever to upload. I want to keep my blog archive if I can. So my first attempt will be to reduce all of my blog images to smaller png files and try that (I'll use Photoshop's batch capabilities after I create an action). Also thanks to the person who told where the Domain file is. Now I can back it up. I would been quite upset to have to rebuild this whole thing.
Happy clickin'
Well I reduced the file size of about half of my blog page graphics from 2-4 each MB to 200-400KB each and I was able to Publish without the app. quitting.
Hooray.
Here's yet another odd quirk. Even though I'm not having problems anymore, I do find if I try and publish changes to a page
without also having made a change of some kind to my blog, I crash. The blog has to be red to do a successful publish of anything on the site.
I'm just praying we will hear something next week at WWDC about a new and improved iWeb (wait -- forget improved, how about just one that works).
Having a similar problem, Domain file: 2.19GB. (I’m a professional web designer, but I bought iWeb so I’d be able to just throw something together and have it look nice. The Domain file is huge because I drag the photos into iWeb at full size, so family and friends can click on the thumbnails and download and print them.)
I will say that it does indeed seem to be an issue of file size, for me. I tried breaking down the Domain file into several smaller files—one for everything but photos (including the main Photos page, which is just a bunch of links), then one for each quarter’s photos (Q4 2005, Q1 2006, etc.) and none of the resulting (<700MB) files have crashed iWeb. Unfortunately, I have yet to devise a system for keeping the various domains synchronized, since the Navigation bar across the top requires at least a placeholder for every page. (Grrr….)
eta: I just looked in the Console, at console.log. Very interesting reading, even if I don’t understand everything it says:
2007-06-09 04:51:42.071 iWeb[747] Doesn't match
2007-06-09 04:51:42.094 iWeb[747] Doesn't match
2007-06-09 04:51:42.095 iWeb[747] Doesn't match
2007-06-09 04:51:42.097 iWeb[747] Doesn't match
2007-06-09 04:51:42.099 iWeb[747] Doesn't match
2007-06-09 04:51:42.101 iWeb[747] Doesn't match
2007-06-09 04:51:42.116 iWeb[747] Doesn't match
2007-06-09 04:51:42.117 iWeb[747] Doesn't match
2007-06-09 04:51:42.130 iWeb[747] Doesn't match
2007-06-09 04:51:42.130 iWeb[747] Doesn't match
iWeb(747,0xa000ed88) malloc:
* vm_allocate(size=9441280) failed (error code=3)
iWeb(747,0xa000ed88) malloc:
* error: can't allocate region
iWeb(747,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
2007-06-09 04:55:02.415 iWeb[747] Could not get bitmap data planes
iWeb(747,0xa000ed88) malloc:
* vm_allocate(size=9441280) failed (error code=3)
iWeb(747,0xa000ed88) malloc:
* error: can't allocate region
iWeb(747,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
2007-06-09 04:55:03.055 iWeb[747] Could not get bitmap data planes
iWeb(747,0xa000ed88) malloc:
* vm_allocate(size=9441280) failed (error code=3)
iWeb(747,0xa000ed88) malloc:
* error: can't allocate region
iWeb(747,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
2007-06-09 04:55:04.573 iWeb[747] Could not get bitmap data planes
iWeb(747,0xa000ed88) malloc:
* vm_allocate(size=21237760) failed (error code=3)
iWeb(747,0xa000ed88) malloc:
* error: can't allocate region
iWeb(747,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
2007-06-09 04:55:05.279 iWeb[747] Could not get bitmap data planes
iWeb(747,0xa000ed88) malloc:
* vm_allocate(size=11878400) failed (error code=3)
iWeb(747,0xa000ed88) malloc:
* error: can't allocate region
iWeb(747,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
Jun 9 04:55:11 {computer name} crashdump[751]: iWeb crashed
Every time I see a crash, it is immediately preceded by at least one occurrence of the following lines (with varying numbers following “size=”, in the first line):
iWeb(728,0xa000ed88) malloc:
* vm
allocate(size=______) failed (error code=3)
iWeb(728,0xa000ed88) malloc:
* error: can't allocate region
iWeb(728,0xa000ed88) malloc:
* set a breakpoint in szone_error to debug
If I had to take a guess, I’d say iWeb is running out of virtual memory while publishing.
I just deleted some superfluous files, leaving 20.8GB available on my hard drive. I then opened Activity Monitor, opened iWeb, made a tiny change, and watched while I saved and published.
While iWeb was simply displaying the site, it was using 2.23 GB of real memory and 2.56 GB of virtual memory. Saving slowly increased these numbers to 2.39 and 2.72, respectively, after which they dropped to 2.22 and 2.55.
Then I published to a folder. The numbers started rising at a fairly normal pace until iWeb finally crashed at 2.93 and 3.29. I tried this a second time with identical results. (Console.log also reported the same messages/errors as mentioned in my previous post.)
I have had the same problems and had to delete quite a few blog entries in order to publish a new one. I spoke to someone at Apple and he suggested I write in a complaint so I urge everyone to do so as well. Here's the link:
I have contacted Apple support, so it will be interesting to see the response. I have a Mac Pro, Intel Quad Core with 6Gb RAM and can't get my site to publish. I've taken a video screen capture and passed it on, so we'll wait & see.
From what I can tell from my own experiments, and plenty of web discussions, is that the error is due to the Blogging portion of iWeb not working as it should. To test, I created 2 new web sites, and relocated them above my failing site.
The first I published a basic home page. Tried this & again it froze on my blog page on the second site.
Then I published a second site, which was between these 2 sites, but this time added a Blog to the Homepage. Crash (Bang Boom). No problems at all until a few months ago -- just can't recall what happened at the time -- if it was an iWeb / OS X / or .Mac update.
I'll keep you all posted if the skinny, trendy guy actually cares enough to respond with anything other than it being yours, yours, yours & my fault (As opposed to the older, balding guy with the calculator).
