Re: really weird move file problem
Re: really weird move file problem
- Subject: Re: really weird move file problem
- From: Dave Hersey <email@hidden>
- Date: Fri, 21 Sep 2007 14:43:49 -0400
Jaime ,
This sounds to me like it could be something completely unrelated to
the file itself. The fact that your application hangs makes it sound
like you could be running up against a lurking memory corruption/
invalid object bug or something that just happens to get triggered at
this time. Or maybe your paths are invalid. (Check the value coming
back from resultFilePath before making the call.)
If that value isn't the problem, I'd rule out the file copy itself by
putting the code early on into your launch (like awakeFromNib:), and
using static path strings pointing to a copy of the problem movie and
the output path:
- (void) awakeFromNib
{
...
NSAssert([[NSFileManager defaultManager]
movePath: @"/ProblemFile.mov"
toPath: @"ProblemFileOut.mov" handler: nil],
@"could not move the media file");
...
}
If the copy functions like that, then there's something else going
on, which seems likely. If the move fails, it shouldn't be able to
hang your app. That indicates something else is going on.
- Dave
On Sep 21, 2007, at 2:03 PM, Jon Hendry wrote:
Is there anything weird about the destination file pathname?
Unusual characters? Spaces?
Does it happen with files of any size?
On Friday, September 21, 2007, at 12:11PM, "Jaime Magiera"
<email@hidden> wrote:
Hi folks,
Very strange scenario: I'm modifying .mov files at the Atom level,
then moving the modded file out of /tmp and into user space with ...
NSAssert([[NSFileManager defaultManager] movePath:workingFilePath
toPath:[self
resultFilePath]
handler: nil],
@"could not move the media file");
On a certain machine, when moving to a second partition, or a
connected firewire device, the file move freaks out and just runs and
runs and runs, with no errors thrown. There is a tmp file in the
final location (the usual "ADFSDL-DUDTYDSHSO" type generated name). I
have to force quit my app. The resulting file is, of course,
unusable. There are no errors in the log. If I select a location on
the same partition for the final file, the move works fine.
At this point, it only appears to happen on one machine -- a MacBook
Pro with HFS+ using GUID partition table. (However, code works fine
on my MacBook Pro with the same formatting)
Can anyone think of possible reasons for this? Any way of
troubleshooting? I'm stumped.
Jaime Magiera
Sensory Research
http://www.sensoryresearch.net
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
40herseyweb.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden