Dear Leon McNeil,
I have expected major crashes in my MPFreaker, they are more and more common, spetially when Itunes is playing and MPFreaker is updating the data.
Itunes 8.2.1 (6)
Anyways, here goes my log.
Please help us with this great piece of software.
Cheers,
Process: MPFreaker [3785]
Path: /Applications/MPFreaker.app/Contents/MacOS/MPFreaker
Identifier: com.lairware.mpfreaker
Version: 1.8.1 (1.8.1)
Code Type: X86 (Native)
Parent Process: launchd [129]
<snip>
Thread 5 Crashed:
0 libobjc.A.dylib 0x95cbb688 objc_msgSend + 24
1 com.apple.CoreFoundation 0x939ff581 _CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation 0x939ed595 CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation 0x939edc78 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x900d1530 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x9006de0d -[NSThread main] + 45
6 com.apple.Foundation 0x9006d9b4 __NSThread__main__ + 308
7 libSystem.B.dylib 0x92210155 _pthread_start + 321
8 libSystem.B.dylib 0x92210012 thread_start + 34
<snip>
Big Bug in Version 1.8.1 (1.8.1)
Known bug in Mac OS X 10.5.7?
This particular crash appears to be a known bug in Mac OS X 10.5.7, we can only hope that Apple fixes it for 10.5.8. Anyone else experiencing a crash is advised to look in the log for the crashing thread and if it looks like this, you're experiencing the same thing:
Thread [n] Crashed:
0 libobjc.A.dylib [addr] objc_msgSend + 24
1 com.apple.CoreFoundation [addr] _CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation [addr] CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation [addr] CFRunLoopRunInMode + 88
4 com.apple.Foundation [addr] +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation [addr] -[NSThread main] + 45
6 com.apple.Foundation [addr] __NSThread__main__ + 308
7 libSystem.B.dylib [addr] _pthread_start + 321
8 libSystem.B.dylib [addr] thread_start + 34
Leon
Thread [n] Crashed:
0 libobjc.A.dylib [addr] objc_msgSend + 24
1 com.apple.CoreFoundation [addr] _CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation [addr] CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation [addr] CFRunLoopRunInMode + 88
4 com.apple.Foundation [addr] +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation [addr] -[NSThread main] + 45
6 com.apple.Foundation [addr] __NSThread__main__ + 308
7 libSystem.B.dylib [addr] _pthread_start + 321
8 libSystem.B.dylib [addr] thread_start + 34
Leon
Yeah, I upgraded to the new MPFreaker and bug continues...
I will upgrade OS and try again,
see:
<snip>
Thread 5 Crashed:
0 libobjc.A.dylib 0x95cbb688 objc_msgSend + 24
1 com.apple.CoreFoundation 0x939ff581 _CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation 0x939ed595 CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation 0x939edc78 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x900d1530 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x9006de0d -[NSThread main] + 45
6 com.apple.Foundation 0x9006d9b4 __NSThread__main__ + 308
7 libSystem.B.dylib 0x92210155 _pthread_start + 321
8 libSystem.B.dylib 0x92210012 thread_start + 34
<snip>
I will upgrade OS and try again,
see:
<snip>
Thread 5 Crashed:
0 libobjc.A.dylib 0x95cbb688 objc_msgSend + 24
1 com.apple.CoreFoundation 0x939ff581 _CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation 0x939ed595 CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation 0x939edc78 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x900d1530 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x9006de0d -[NSThread main] + 45
6 com.apple.Foundation 0x9006d9b4 __NSThread__main__ + 308
7 libSystem.B.dylib 0x92210155 _pthread_start + 321
8 libSystem.B.dylib 0x92210012 thread_start + 34
<snip>
Tiger?
Your crash logs indicate you're using Leopard (10.5.x), right?
I'm so pleased to hear that Apple has resolved this bug.
(Edited thread to remove overwhelming amount of irrelevant crash log stuff)
I'm so pleased to hear that Apple has resolved this bug.
(Edited thread to remove overwhelming amount of irrelevant crash log stuff)
Follow me at: http://twitter.com/lairware