Intemittent issues with ejecting CD's.

[solefald]

Hello,

I've been experiencing this issue for a while now, but was under the impression that it was related to my old computer, however, after purchasing new MacBook Pro, Amadeus Pro still displays the same behavior.
The issue is intermittent, but consistently reproducible.

When burning CD's, after recording is done, Amadeus Pro ejects the CD, however, Burning Status window never goes away. Inserting another blank CD into the drive, at this point immediately causes Amadeus to become a zombie process and killing it is impossible, unless you reboot the computer.

Force Quit does not help, killing the process via Terminal does not help either, and `ps' shows the process is "(AmadeusPro)" which is a typical Unix sign of a Zombie process. Those never go away, and it's impossible to kill them and in alot of cases these are related to hardware not being released by a certain driver or process

Now, i found a strange workaround that helps, but would be nice if these stopped happening.

As soon as it ejects the CD and you see that the Burning Dialog still there, exit Amadeus, hit the Eject button on the keyboard so you hear mechanism try to eject the CD. After that re-open Amadeus and it's back to normal.

How often does it happen? Often enough to piss me off haha
I am burning my new dj mix and so far burned about 20-25 CD's today.
During that time I had to quit from Amadeus 6 times, so to me its pretty serious.


I am burning a 153Mb Amadeus file, with 16 markers, at 8x speed on a brand new MacBook Pro, but I dont think it is hardware related. My old MBP (1st gen Intel) experiences exact same issue with same consistency.


thanks
igor

[Martin Hairer]

Hi Igor,

Force Quit does not help, killing the process via Terminal does not
help either, and `ps' shows the process is "(AmadeusPro)" which is a
typical Unix sign of a Zombie process. Those never go away, and it's
impossible to kill them and in alot of cases these are related to
hardware not being released by a certain driver or process

Now, i found a strange workaround that helps, but would be nice if
these stopped happening.

From your description, it does sound somewhat like a system /
driver / hardware issue, but there is of course always the possibility
that Amadeus Pro does something weird. Next time this happens, could
you select Amadeus Pro in the Activity Monitor hit "Sample Process"
and send that back to me? It might give a clue as to where the problem
lies. Thanks,

Martin

HairerSoft
http://www.hairersoft.com/


_______________________________________________
Amadeus forum mailing list
Unsubscribe / change settings at http://two.pairlist.net/mailman/listinfo/forum_list

[Lou Kash]

MBP's super slim slot loading burners are known to be a bit flaky. I bought a MBP last fall (one of the last with matte display…). And on the 3rd attempt the Apple service provider finally got me a working DVD burner. The service guy confirmed that they are replacing them quite frequently. Initially, my brand new MBP wasn't even able to load the original Apple installation DVDs.

[solefald]

Next time this happens, could
you select Amadeus Pro in the Activity Monitor hit "Sample Process"
and send that back to me? It might give a clue as to where the problem
lies.

Here you go

Code: Select all

Sampling process 21450 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Amadeus Pro (pid 21450) every 1 millisecond
Call graph:
    1883 Thread_2503
      1883 start
        1883 _start
          1883 NSApplicationMain
            1883 -[NSApplication run]
              1883 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
                1883 _DPSNextEvent
                  1883 BlockUntilNextEventMatchingListInMode
                    1883 ReceiveNextEventCommon
                      1883 RunCurrentEventLoopInMode
                        1883 CFRunLoopRunInMode
                          1883 CFRunLoopRunSpecific
                            1883 mach_msg
                              1883 mach_msg_trap
                                1883 mach_msg_trap
    1883 Thread_2603
      1883 thread_start
        1883 _pthread_start
          1883 kevent
            1883 kevent
    1883 Thread_2703
      1883 thread_start
        1883 _pthread_start
          1883 fe_fragment_thread
            1883 pthread_cond_wait$UNIX2003
              1883 __semwait_signal
                1883 __semwait_signal
    1883 Thread_2803
      1883 thread_start
        1883 _pthread_start
          1883 __NSThread__main__
            1883 -[NSThread main]
              1883 -[NSUIHeartBeat _heartBeatThread:]
                1883 -[NSConditionLock lockWhenCondition:]
                  1883 -[NSConditionLock lockWhenCondition:beforeDate:]
                    1883 -[NSCondition waitUntilDate:]
                      1883 pthread_cond_timedwait_relative_np
                        1883 _pthread_cond_wait
                          1883 semaphore_timedwait_signal_trap
                            1883 semaphore_timedwait_signal_trap
    1883 Thread_2903
      1883 thread_start
        1883 _pthread_start
          1883 DRThreadObject::StartRoutine(DRThreadObject*)
            1883 DRWorkLoop::WorkLoopEntry(DRWorkLoop*)
              1883 DRWorkLoop::WorkLoop()
                1883 CFRunLoopRun
                  1883 CFRunLoopRunSpecific
                    1883 mach_msg
                      1883 mach_msg_trap
                        1883 mach_msg_trap

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
        mach_msg_trap        3766
        __semwait_signal        1883
        kevent        1883
        semaphore_timedwait_signal_trap        1883
Sample analysis of process 21450 written to file /dev/stdout