Bug 2109 – mov123 on 10.4.2 fails

Bug 2109 - mov123 on 10.4.2 fails

Summary:

mov123 on 10.4.2 fails

Status:	RESOLVED WONTFIX

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Transcoding
Version:	6.2.0
Platform:	Macintosh MacOS X 10.4

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-09-09 09:51 UTC by Dan Sully
Modified:	2005-09-14 22:10 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
mov123 crash log (27.54 KB, application/octet-stream) 2005-09-11 15:32 UTC, Dan Sully	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Sully 2005-09-09 09:51:49 UTC

Finding this in the log:

2005-09-08 23:12:12.425 mov123[371] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 
(0x44c), port = 0x4a17, name = 
'com.apple.audio.CoreAudio.pid-371.1940779190.2015.Telemetry.IOCycle'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2005-09-08 23:12:12.426 mov123[371] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach 
port (com.apple.audio.CoreAudio.pid-371.1940779190.2015.Telemetry.IOCycle)

Comment 1 Blackketter Dean 2005-09-09 10:01:32 UTC

is this every invocation or with a particular file?  I get a crash if I don't give it a file to decode, but seems 
to work otherwise.

Comment 2 Dan Sully 2005-09-09 10:02:57 UTC

I need to test more - but seems to be every file.

Comment 3 Blackketter Dean 2005-09-09 10:13:37 UTC

Ok, I can't reproduce here.

Comment 4 Dan Sully 2005-09-09 12:16:28 UTC

http://electricrain.com/daniel/bug2109.m4a

Comment 5 Dan Sully 2005-09-11 15:32:56 UTC

Created attachment 814 [details]
mov123 crash log

Here's the crash log (a few actually) from mov123. Hopefully this will give a
clue.

Comment 6 Blackketter Dean 2005-09-14 12:43:18 UTC

Wow, that's deep in "NewMovieFromFile" and I can't reproduce it here...

Comment 7 Dan Sully 2005-09-14 13:03:19 UTC

The issue appears to have gone away after upgrading to QT 7.0.2

Comment 8 Blackketter Dean 2005-09-14 22:10:57 UTC

Hm, appears to be a quicktime bug.