Aperture crashing during Flickr export
Aperture is crashing during export using b23. I am exporting Raw images from an EOS 40D and Aperture is crashing with no warning or error message each time this is repeated.
The OS is 10.5.2 and Aperture is version 2.1 with b23 installed.
The OS is 10.5.2 and Aperture is version 2.1 with b23 installed.
10 people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company is aware of this problem.
-
Inappropriate?I've just looked into Console to see what happens when Aperture crashes. It reports the following:
03/05/2008 12:13:33 com.apple.launchd[113] ([0x0-0x32032].com.apple.Aperture[200]) Exited abnormally: Broken pipe -
Inappropriate?I've uploaded a new set of photos today and again had a broken pipe problem. I was able to upload one different photo last night which was slightly strange.
-
Inappropriate?Same here, although I can sometimes get an export to run OK if I restart and attempt it again. This was happening with v2 so I hoped the beta version would fix it but sadly not :(
Here's my console error message FWIW:
05/05/2008 20:40:19 com.apple.launchd[114] ([0x0-0x2a02a].com.apple.Aperture[204]) Exited abnormally: Broken pipe
Edit:
After enabling debugging here's what I got:
05/05/2008 20:54:02 Aperture[238] Headers written
05/05/2008 20:54:02 Aperture[238] Upload progress: 0 of 2748644
05/05/2008 20:54:37 Aperture[238] Upload progress: 640000 of 2748644
05/05/2008 20:55:20 Aperture[238] Upload progress: 1280000 of 2748644
05/05/2008 20:56:04 Aperture[238] Upload progress: 1920000 of 2748644
05/05/2008 20:56:14 com.apple.launchd[114] ([0x0-0x34034].com.apple.Aperture[238]) Exited abnormally: Broken pipe
I’m annoyed
-
Inappropriate?Same broken pipe message........
Why has this just started to happen? I have been uploading photos with FlickrExport for months and months with no problem. I have even left it uploading all night with dozens of large files............Now it's started to play up!!
-
Inappropriate?A broken pipe can happen when the connection is unexpectedly closed and FlickrExport continues to try and send data. I'll see what I can do to prevent this from happening.
Possible reasons this is happening to you include: a firewall or router that's terminating the connection, or a web proxy that limits the size of an HTTP POST body.
I’m hoping to do better.
-
Thanks for the update Fraser. It's odd how for Garth and I it's just started happening out of the blue. -
Thanks Fraser. It must be difficult to design something that can deal with every eventuality and system configuration! -
It really is. Especially when you only control one end of the entire system :-) -
Inappropriate?I've just come across this thread, I don't know if it has any bearing on why our problems have just started!?!
http://www.flickr.com/help/forum/en-u...
1 person says
this solves the problem
-
Inappropriate?Thanks for the pointer. That has got me to a solution that is allowing me to upload as a workaround.
I am with Virgin Media (formerly Blueyonder) and recently found that I was unable to connect to my del.icio.us bookmarks unless I used a blueyonder proxy server. Similarly other Virgin Media users I know had exactly the same problem. I raised this with tech support and it was escalated and then magically fixed. I couldn’t see and reason why one HAD to use a proxy to connect to a site.
While I couldn’t upload a single image to Flickr tonight once I enabled the proxy connection in network prefs I was able to upload six with no problem. Again, I don’t see why I should have to do this.
It sounds like Flickr are on the case which is a good thing as I imagine they have the clout to get it fixed. I will contact them again in any case.
Cheers.
I’m thankful
1 person says
this solves the problem
-
Inappropriate?Garth,
Thanks for the link. That certainly matches what I know about this issue. I'm going to mark this thread as 'we're aware of it' for now.
I’m on Virgin Media myself and not a huge fan.
-
I'm not a fan either, I was thinking of switching to sky but they don't seem to fair much better!! :) -
Inappropriate?As far as I can tell I can still upload to Flickr via Safari without using a proxy. Is there any reason why those transfers are unaffected?
-
Inappropriate?Overnight, Aperture went 'poof' after uploading 29 photos out of a batch of 40. Curiously, it doesn't seem to have spawned a crash log. Second time this has happened to me out of two medium-batch exports.
I'm in the UK but with Pipex, who I haven't yet seen named as currently problematic with Flickr. Aperture 2.1, FlickrExport 1.0.9 for Aperture.
Fraser - is there anything I can do to help collect information for you?
I’m meh, flakiness is a fact of life.
-
Inappropriate?I, too, have suddenly developed a problem with Aperture crashing during Flickr Export uploading.
I have one symptom that seems to be unique. Or, at least, no one's written of it yet. When I open a FlickrExport event, it will go the "authentication" action, and then I'll get a message that it was not able to get correctly connected. I have to open the FlickrExport event again, and then it will authenticate with Flickr.
This behavior is consistent: first time failure to authenticate, second time success.
And then, if I'm uploading more than one shot, it will crash somewhere in the line of pictures getting uploaded. I've never had it mess up when only uploading a single shot, but any time I'm doing a lot of uploading, I'm going to see this problem.
Some times when this happens, I get the report from Aperture that it closed unintentionally on its last use, but mostly I don't.
I had also finally bought a license for the full version of FlickrExport, and applied it. Is it possible something got corrupted in applying the license key?
I’m unhappy
-
Inappropriate?Oops--sorry, there are mornings my brain should be in a jar.
I'm using Aperture 2.1 under Leopard 10.5.3, and using the latest non-beta version of FlickrExport. -
Inappropriate?Hi All -
I'm having the same problem too with Aperture 2.1, Mac OS X 10.5.3 and Flickr Export 1.0.9.
Console Errors after the crash:
7/7/08 10:01:26 AM com.apple.launchd[77] ([0x0-0x120120].com.apple.Aperture[15564]) Exited abnormally: Broken pipe
7/7/08 10:02:01 AM [0x0-0x12a12a].com.apple.Aperture[15792] Mon Jul 7 10:02:01 Aperture[15792] CGContextGetType: invalid context
I’m frustrated
-
Inappropriate?I have this problem and have found that it is only happening with one particular image that I am trying to upload. It turns out that if I choose the "Flickr 10Mb" option it doesn't happen. I have a pro account, so I guess the version that I am uploading exceeds the 20Mb limit imposed by Flickr. I have no idea how the API works, but I guess maybe Flickr are just closing the socket once 20Mb of data has been uploaded. Hopefully there is some way of handling it gracefully.
I’m sure it's something that can be fixed soon.
-
Inappropriate?I am having the same problem. Aperture crashes during the upload. It is not a file size problem.
Ben Cutshall -
Inappropriate?The exact cause of this problem is that Aperture isn't handling the SIGPIPE signal and FlickrExport doesn't handle it either.
I have a bug open on this, and I'm really sorry for the inconvenience.
I’m overloaded with iPhone.
-
Inappropriate?Thanks for the update, Fraser - good to know the problem is identified, at least.
Loading Profile...



EMPLOYEE





