Apple Intelligence is now available on iPhone, iPad, and Mac!

⏺ Join the discussion

⏺ Press release 

⏺ Learn more

⏺ Watch the video

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Two Different Pandora Apps Hang on MacBook (Crashlog Help)

Hello,


Please let me first apologize in advance for the length of the post. This post covers what the problem is, what I've already done to troubleshoot, and a sample log from both of the Pandora apps I have that are constantly losing connectivity and crashing. I should probably clarify right off the bat that I am not a Pandora subscriber and I am not streaming off the website. This question pertains to the behavior of two different stand-alone apps that I've tried to use on my mid-2012 "classic" MacBook Pro after recently installing a fresh copy of El Capitan. (Up until recently I was still using Snow Leopard so please bear with me :-).


The Problem…


"HD Radio for Pandora", downloaded from the App Store little over a week ago, and the open-source "Hermes" (the most current version), exhibit the same problem: They loose connection and crash outright after about 7 minutes of playback. I first see an error that Pandora’s server connection has failed. Sometimes playback becomes choppy in the minutes before it disconnects. Ultimately, the entire app crashes and prompts me to send a report to Apple.


The Suspects…


Initially I suspected Microsoft OneDrive because that’s the more recent addition to the MacBook. I thought that perhaps OneDrive’s background activity (to the Cloud) was “choking” the connections somehow. I don’t have OneDrive installed on my iMac and on that machine I have no problems running the same Pandora app under El Cap. However, when I googled “Pandora” and “OneDrive” I couldn’t find any other complaints that there is a clash between the apps (and it seems unlikely I would be the first one). So instead of uninstalling OneDrive I applied the latest updates. (That didn’t help, though.)


It occurs to me it could be a sleep/network timeout issue with the MacBook cutting off the streaming at a certain point after I walk away (usually when the computer is idle). But I am not adept enough at interpreting OS X crashlogs to confirm one way or another.


I then thought it could be the use of BinaryAge “TotalFinder”. TotalFinder is a Finder replacement and the current version relies on disabling SIP. Somehow I have SIP running alongside TF simultaneously, which according to the developer shouldn’t be possible (indeed, I tried to accomplish the same on my El Cap install on the iMac and after startup SIP keeps flashing a notice that TF has been disabled so essentially TF is not running on my iMac, whereas on the MacBook the crash log indicates that SIP *is enabled* despite running TF). Again, however, my limited knowledge of how to read OS X crash logs doesn’t seem to point to TF (it’s not mentioned in the reports).


I next thought that it could be a weak connection over my wi-fi even though I have full-strength bars on my MacBook for my home wi-fi. I do note that my iHeart app gets choppy at times over this same Internet connection to the MacBook — but unlike the Pandora apps iHeart never crashes outright. My iMac, which has no problem streaming through either Pandora app (Hermes on Snow Leopard, HD Radio for Pandora on the El Cap partition), is wired to the router by ethernet whereas the MacBook is on wi-fi. As a result, I'm not ready to rule out that the connection is unstable, I just don't have enough to go on either way at this point.


My Troubleshooting efforts…


1) Uninstalling/reinstalling the two Pandora apps (using "TrashMe" from the App Store to make sure they uninstall completely);

2) Making sure I am signed out other Pandora apps running on the same network;

3) Holding down the option+shift keys while launching the Pandora apps to rebuild app preferences;

4) Turning off file sharing on the MacBook (had no effect);

5) In Hermes, I went into the app preferences and tried enabling “audio by proxy” but that didn’t help, either.


One website suggested rebuilding system Audio file prefs. According to that website there should have been two files stored in the Library > “Audio” subfolder (which I found and trashed) and a third plist containing the words “audio toolbox” in the main body of the Preferences folder but I don’t find a file by that name in my Library > Preferences folder. And so I am here because none of my own troubleshooting efforts have helped. 😐


A Tale of Two Crash Logs…


FIRST REPORT:


Process: HD Radio for Pandora [1814]

Path: /Applications/HD Radio for Pandora.app/Contents/MacOS/HD Radio for Pandora

Identifier: com.anobot.Pandora

Version: 1.0.0 (3)

App Item ID: 1122222008

App External ID: 817712257

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: HD Radio for Pandora [1814]

User ID: 501


Date/Time: 2016-12-28

OS Version: Mac OS X 10.11.6 (15G1212)

Report Version: 11

Anonymous UUID: … edited out …


Sleep/Wake UUID: ACDB05F0-B09A-45A3-B0C1-8A3D64D1180F


Time Awake Since Boot: 13000 seconds

Time Since Wake: 3800 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Exception Note: EXC_CORPSE_NOTIFY


Global Trace Buffer (reverse chronological seconds):


15.777957 CFNetwork 0x00007fff870b3db3 TCP Conn 0x7fd2b914a680 SSL Handshake DONE

15.778751 CFNetwork 0x00007fff870b2659 TCP Conn 0x7fd2b91e3480 complete. fd: 9, err: 0

15.778795 CFNetwork 0x00007fff87140f33 TCP Conn 0x7fd2b91e3480 event 1. err: 0

15.854598 CFNetwork 0x00007fff870b3c8f TCP Conn 0x7fd2b914a680 starting SSL negotiation

15.854857 CFNetwork 0x00007fff870b2659 TCP Conn 0x7fd2b914a680 complete. fd: 10, err: 0

15.855093 CFNetwork 0x00007fff87140f33 TCP Conn 0x7fd2b914a680 event 1. err: 0

15.976793 CFNetwork 0x00007fff870b192b TCP Conn 0x7fd2b914a680 started

15.978039 CFNetwork 0x00007fff870b192b TCP Conn 0x7fd2b91e3480 started

228.940454 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3243a00] Releasing session

228.940637 AppleJPEG 0x00007fff91b73a11 [0x7fd2b40ebc00] Releasing session

228.940673 AppleJPEG 0x00007fff91b73a11 [0x7fd2b2990a00] Releasing session

228.944474 AppleJPEG 0x00007fff91b7611c [0x7fd2b3145000] Decoding completed without errors

228.944474 AppleJPEG 0x00007fff91b740fc [0x7fd2b3145000] Options: 8x-1 [FFFFFFFF,FFFFFFFF] 0001D060

228.944474 AppleJPEG 0x00007fff91b73fae [0x7fd2b3145000] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 50025

228.946047 AppleJPEG 0x00007fff91b7305e [0x7fd2b3145000] Created session

228.946589 AppleJPEG 0x00007fff91b7305e [0x7fd2b40ebc00] Created session

229.088349 CFNetwork 0x00007fff870b2659 TCP Conn 0x7fd2b8e62220 complete. fd: 15, err: 0

229.088631 CFNetwork 0x00007fff87140f33 TCP Conn 0x7fd2b8e62220 event 1. err: 0

229.138662 CFNetwork 0x00007fff870b192b TCP Conn 0x7fd2b8e62220 started

229.160126 AppleJPEG 0x00007fff91b73a11 [0x7fd2b2800a00] Releasing session

229.160463 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3145000] Releasing session

229.160702 AppleJPEG 0x00007fff91b7305e [0x7fd2b3145000] Created session

229.181657 AppleJPEG 0x00007fff91b7611c [0x7fd2b2800a00] Decoding completed without errors

229.181657 AppleJPEG 0x00007fff91b740fc [0x7fd2b2800a00] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060

229.181657 AppleJPEG 0x00007fff91b73fae [0x7fd2b2800a00] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 60126

229.183999 AppleJPEG 0x00007fff91b73a11 [0x7fd2b2a14e00] Releasing session

229.183999 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3aa2a00] Releasing session

229.183999 AppleJPEG 0x00007fff91b73a11 [0x7fd2b29a9200] Releasing session

229.183999 AppleJPEG 0x00007fff91b73a11 [0x7fd2b28e8000] Releasing session

229.184004 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3a5bc00] Releasing session

229.184051 AppleJPEG 0x00007fff91b73a11 [0x7fd2b40dba00] Releasing session

229.184408 AppleJPEG 0x00007fff91b73a11 [0x7fd2b39e2200] Releasing session

229.184408 AppleJPEG 0x00007fff91b73a11 [0x7fd2b314fe00] Releasing session

229.184408 AppleJPEG 0x00007fff91b73a11 [0x7fd2b4183800] Releasing session

229.184611 AppleJPEG 0x00007fff91b73a11 [0x7fd2b29ef800] Releasing session

229.184611 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3074000] Releasing session

229.184611 AppleJPEG 0x00007fff91b73a11 [0x7fd2b3ab4800] Releasing session


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.audio.toolbox.AudioToolbox 0x00007fff9159b285 MP3AudioStream::GeneratePackets(AudioFileStreamContinuation&) + 1527

1 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157f630 AudioFileStreamObject::ParseBytes(unsigned int, AudioFileStreamContinuation&) + 108

2 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157eebf AudioFileStreamWrapper::ParseBytes(unsigned int, void const*, unsigned int) + 97

3 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157ce14 AudioFileStreamParseBytes + 78

4 com.anobot.Pandora 0x0000000100ab4033 0x100a82000 + 204851

5 com.apple.CoreFoundation 0x00007fff83a04ff4 _signalEventSync + 180

6 com.apple.CoreFoundation 0x00007fff83a215db _cfstream_solo_signalEventSync + 251

7 com.apple.CoreFoundation 0x00007fff83a0285c _CFStreamSignalEvent + 476

8 com.apple.CoreFoundation 0x00007fff83a04ff4 _signalEventSync + 180

9 com.apple.CoreFoundation 0x00007fff83a221fe _cfstream_shared_signalEventSync + 478

10 com.apple.CoreFoundation 0x00007fff839e37e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

11 com.apple.CoreFoundation 0x00007fff839c2f1c __CFRunLoopDoSources0 + 556

12 com.apple.CoreFoundation 0x00007fff839c243f __CFRunLoopRun + 927

13 com.apple.CoreFoundation 0x00007fff839c1e38 CFRunLoopRunSpecific + 296

14 com.apple.HIToolbox 0x00007fff93e8e935 RunCurrentEventLoopInMode + 235

15 com.apple.HIToolbox 0x00007fff93e8e76f ReceiveNextEventCommon + 432

16 com.apple.HIToolbox 0x00007fff93e8e5af _BlockUntilNextEventMatchingListInModeWithFilter + 71

17 com.apple.AppKit 0x00007fff9726ddf6 _DPSNextEvent + 1067

18 com.apple.AppKit 0x00007fff9726d226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

19 com.apple.AppKit 0x00007fff97261d80 -[NSApplication run] + 682

20 com.apple.AppKit 0x00007fff9722b368 NSApplicationMain + 1176

21 libdyld.dylib 0x00007fff96f245ad start + 1


…


Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x700007fd2b931b9e rbx: 0x00000000000004e6 rcx: 0x00000000002f4180 rdx: 0x00000000000004e6

rdi: 0x00007fd2b306e200 rsi: 0x0000000100ae0130 rbp: 0x00007fff5f17ba40 rsp: 0x00007fff5f17b960

r8: 0x0000000000000006 r9: 0x0000000000000000 r10: 0x00007fd2b4048310 r11: 0x0000000100b0e608

r12: 0x00000000000004e6 r13: 0x0000000000000003 r14: 0x00007fd2b8948da0 r15: 0x00007fd2b8948da8

rip: 0x00007fff9159b285 rfl: 0x0000000000010246 cr2: 0x0000000101638000


Logical CPU: 6

Error Code: 0x00000000

Trap Number: 13



SECOND REPORT:


Similar crashlog is generated every time I try to run Hermes, however in this log I do not omit Threads "1::" through "8::" (which were omitted above for brevity):


Process: Hermes [1297]

Path: /Users/USER/Downloads/Hermes.app/Contents/MacOS/Hermes

Identifier: com.alexcrichton.Hermes

Version: 1.3.0 (2056)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Hermes [1297]

User ID: 501


Date/Time: 2016-12-27

OS Version: Mac OS X 10.11.6 (15G1212)

Report Version: 11

Anonymous UUID: … edited out …


Sleep/Wake UUID: 0F2D7F10-BA2C-4378-93A5-1696905C1CCF


Time Awake Since Boot: 4200 seconds

Time Since Wake: 2100 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000007f9fba59879

Exception Note: EXC_CORPSE_NOTIFY


VM Regions Near 0x7f9fba59879:

Process Corpse Info 000000011aac4000-000000011acc4000 [ 2048K] rw-/rwx SM=COW

-->

STACK GUARD 0000700000000000-0000700000001000 [ 4K] ---/rwx SM=NUL stack guard for thread 7


Global Trace Buffer (reverse chronological seconds):

0.499574 AppleJPEG 0x00007fff91b7611c [0x7f9fbc262a00] Decoding completed without errors

0.499574 AppleJPEG 0x00007fff91b740fc [0x7f9fbc262a00] Options: 500x500 [FFFFFFFF,FFFFFFFF] 0001D060

0.499574 AppleJPEG 0x00007fff91b73fae [0x7f9fbc262a00] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 36711

0.499970 AppleJPEG 0x00007fff91b7305e [0x7f9fbc262a00] Created session

15.563986 CFNetwork 0x00007fff870b2659 TCP Conn 0x7f9fba411e80 complete. fd: 9, err: 0

15.564025 CFNetwork 0x00007fff87140f33 TCP Conn 0x7f9fba411e80 event 1. err: 0

15.601364 AppleJPEG 0x00007fff91b73a11 [0x7f9fbba0f600] Releasing session

15.602032 CFNetwork 0x00007fff870b192b TCP Conn 0x7f9fba411e80 started

15.645397 AppleJPEG 0x00007fff91b7611c [0x7f9fbba0f600] Decoding completed without errors

15.648537 AppleJPEG 0x00007fff91b740fc [0x7f9fbba0f600] Options: 500x500 [FFFFFFFF,FFFFFFFF] 0001D060

15.648537 AppleJPEG 0x00007fff91b73fae [0x7f9fbba0f600] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 36711

15.652258 AppleJPEG 0x00007fff91b7305e [0x7f9fbba0f600] Created session

15.743287 AppleJPEG 0x00007fff91b7611c [0x7f9fbc243000] Decoding completed without errors

15.743287 AppleJPEG 0x00007fff91b740fc [0x7f9fbc243000] Options: 500x500 [FFFFFFFF,FFFFFFFF] 0001D060

15.743287 AppleJPEG 0x00007fff91b73fae [0x7f9fbc243000] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 36711

15.743287 AppleJPEG 0x00007fff91b7305e [0x7f9fbc243000] Created session

282.283113 AppleJPEG 0x00007fff91b7611c [0x7f9fbc1ba200] Decoding completed without errors

282.283310 AppleJPEG 0x00007fff91b740fc [0x7f9fbc1ba200] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060

282.283310 AppleJPEG 0x00007fff91b73fae [0x7f9fbc1ba200] Decoding: C0 0x01F401F4 0x0000304A 0x22111100 0x00000000 36711


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.audio.toolbox.AudioToolbox 0x00007fff9159b285 MP3AudioStream::GeneratePackets(AudioFileStreamContinuation&) + 1527

1 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157f630 AudioFileStreamObject::ParseBytes(unsigned int, AudioFileStreamContinuation&) + 108

2 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157eebf AudioFileStreamWrapper::ParseBytes(unsigned int, void const*, unsigned int) + 97

3 com.apple.audio.toolbox.AudioToolbox 0x00007fff9157ce14 AudioFileStreamParseBytes + 78

4 com.alexcrichton.Hermes 0x000000010563bcbd -[AudioStreamer handleReadFromStream:eventType:] + 1008

5 com.apple.CoreFoundation 0x00007fff83a04ff4 _signalEventSync + 180

6 com.apple.CoreFoundation 0x00007fff83a215db _cfstream_solo_signalEventSync + 251

7 com.apple.CoreFoundation 0x00007fff83a0285c _CFStreamSignalEvent + 476

8 com.apple.CoreFoundation 0x00007fff83a04ff4 _signalEventSync + 180

9 com.apple.CoreFoundation 0x00007fff83a221fe _cfstream_shared_signalEventSync + 478

10 com.apple.CoreFoundation 0x00007fff839e37e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

11 com.apple.CoreFoundation 0x00007fff839c2f1c __CFRunLoopDoSources0 + 556

12 com.apple.CoreFoundation 0x00007fff839c243f __CFRunLoopRun + 927

13 com.apple.CoreFoundation 0x00007fff839c1e38 CFRunLoopRunSpecific + 296

14 com.apple.HIToolbox 0x00007fff93e8e935 RunCurrentEventLoopInMode + 235

15 com.apple.HIToolbox 0x00007fff93e8e76f ReceiveNextEventCommon + 432

16 com.apple.HIToolbox 0x00007fff93e8e5af _BlockUntilNextEventMatchingListInModeWithFilter + 71

17 com.apple.AppKit 0x00007fff9726ddf6 _DPSNextEvent + 1067

18 com.apple.AppKit 0x00007fff9726d226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

19 com.apple.AppKit 0x00007fff97261d80 -[NSApplication run] + 682

20 com.apple.AppKit 0x00007fff9722b368 NSApplicationMain + 1176

21 libdyld.dylib 0x00007fff96f245ad start + 1


Thread 1:: Dispatch queue: com.apple.libdispatch-manager

0 libsystem_kernel.dylib 0x00007fff92e93efa kevent_qos + 10

1 libdispatch.dylib 0x00007fff96d04165 _dispatch_mgr_invoke + 216

2 libdispatch.dylib 0x00007fff96d03dcd _dispatch_mgr_thread + 52


Thread 2:: com.apple.NSURLConnectionLoader

0 libsystem_kernel.dylib 0x00007fff92e8cf72 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff92e8c3b3 mach_msg + 55

2 com.apple.CoreFoundation 0x00007fff839c3124 __CFRunLoopServiceMachPort + 212

3 com.apple.CoreFoundation 0x00007fff839c25ec __CFRunLoopRun + 1356

4 com.apple.CoreFoundation 0x00007fff839c1e38 CFRunLoopRunSpecific + 296

5 com.apple.CFNetwork 0x00007fff87078a6d +[NSURLConnection(Loader) _resourceLoadLoop:] + 412

6 com.apple.Foundation 0x00007fff90355e64 __NSThread__start__ + 1351

7 libsystem_pthread.dylib 0x00007fff92da899d _pthread_body + 131

8 libsystem_pthread.dylib 0x00007fff92da891a _pthread_start + 168

9 libsystem_pthread.dylib 0x00007fff92da6351 thread_start + 13


Thread 3:

0 libsystem_kernel.dylib 0x00007fff92e8cf72 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff92e8c3b3 mach_msg + 55

2 com.apple.CoreFoundation 0x00007fff839c3124 __CFRunLoopServiceMachPort + 212

3 com.apple.CoreFoundation 0x00007fff839c25ec __CFRunLoopRun + 1356

4 com.apple.CoreFoundation 0x00007fff839c1e38 CFRunLoopRunSpecific + 296

5 com.apple.CoreFoundation 0x00007fff83a03911 CFRunLoopRun + 97

6 com.apple.Foundation 0x00007fff90355e64 __NSThread__start__ + 1351

7 libsystem_pthread.dylib 0x00007fff92da899d _pthread_body + 131

8 libsystem_pthread.dylib 0x00007fff92da891a _pthread_start + 168

9 libsystem_pthread.dylib 0x00007fff92da6351 thread_start + 13


Thread 4:: com.apple.NSEventThread

0 libsystem_kernel.dylib 0x00007fff92e8cf72 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff92e8c3b3 mach_msg + 55

2 com.apple.CoreFoundation 0x00007fff839c3124 __CFRunLoopServiceMachPort + 212

3 com.apple.CoreFoundation 0x00007fff839c25ec __CFRunLoopRun + 1356

4 com.apple.CoreFoundation 0x00007fff839c1e38 CFRunLoopRunSpecific + 296

5 com.apple.AppKit 0x00007fff973c3d95 _NSEventThread + 149

6 libsystem_pthread.dylib 0x00007fff92da899d _pthread_body + 131

7 libsystem_pthread.dylib 0x00007fff92da891a _pthread_start + 168

8 libsystem_pthread.dylib 0x00007fff92da6351 thread_start + 13


Thread 5:: com.apple.CFSocket.private

0 libsystem_kernel.dylib 0x00007fff92e9307a __select + 10

1 com.apple.CoreFoundation 0x00007fff83a0045a __CFSocketManager + 762

2 libsystem_pthread.dylib 0x00007fff92da899d _pthread_body + 131

3 libsystem_pthread.dylib 0x00007fff92da891a _pthread_start + 168

4 libsystem_pthread.dylib 0x00007fff92da6351 thread_start + 13


Thread 6:

0 libsystem_kernel.dylib 0x00007fff92e935e2 __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92da8578 _pthread_wqthread + 1283

2 libsystem_pthread.dylib 0x00007fff92da6341 start_wqthread + 13


Thread 7:

0 libsystem_kernel.dylib 0x00007fff92e935e2 __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92da8578 _pthread_wqthread + 1283

2 libsystem_pthread.dylib 0x00007fff92da6341 start_wqthread + 13


Thread 8:

0 libsystem_kernel.dylib 0x00007fff92e935e2 __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff92da8578 _pthread_wqthread + 1283

2 libsystem_pthread.dylib 0x00007fff92da6341 start_wqthread + 13


Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x000007f9fba59811 rbx: 0x0000000000000688 rcx: 0x0000000000000000 rdx: 0x0000000000000688

rdi: 0x00007f9fbba0d400 rsi: 0x000000010564cc5f rbp: 0x00007fff5a5e2a60 rsp: 0x00007fff5a5e2980

r8: 0x0000000000000006 r9: 0x0000000000000000 r10: 0x00007f9fbb0051f0 r11: 0x000000010566a3a8

r12: 0x0000000000000688 r13: 0x0000000000000004 r14: 0x00007f9fbf012e50 r15: 0x00007f9fbf012e58

rip: 0x00007fff9159b285 rfl: 0x0000000000010246 cr2: 0x000007f9fba59879


Logical CPU: 2

Error Code: 0x00000004

Trap Number: 14



Please let me know if the above crashlogs provide any more insight. Meanwhile, please accept my apologies for the length of the post.


Thank you.

MacBook Pro, OS X El Capitan (10.11.6), mid 2012

Posted on Dec 28, 2016 1:48 PM

Reply
Question marked as Top-ranking reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Posted on Jan 5, 2017 5:25 PM

Final post to this topic for those who come along later in search of a solution to a similar issue:


I located Apple's official stance on sleeping a "portable". It explains why my experience with my MBP is so much different than what is normal on my iMac even though I'm running El Cap on both:


Portable computers have no network connectivity when in sleep mode, but can wake if the Energy Saver option "Wake for network access" is enabled. If you wish to use file sharing or don't want to interrupt your Internet connection, you should not manually put the computer to sleep, and you should drag the "Computer sleep" slider to Never.

Source: About Energy Saver sleep and idle modes in Mac OS X - Apple Support

Originally, there were two issues that prompted this topic: 1) Both Pandora apps I installed simply disconnected and stopped streaming. 2) Both crashed upon sleep/wake. Most — but not all — of the crashing stopped by removing a third-party audio driver (Soundflower). And yet with continued use I found that HD Radio for Pandora and Hermes were still experiencing a few too many crashes associated with the *normal behavior* of my MBP to disconnect from wi-fi on sleep.

My view on this from the outset was that it shouldn't be necessary to alter ALL Energy Saver sleep settings just to make one type of app work. It turns out that the developers may have dropped the ball on both the apps I have been using by not encoding the proper Assertions. So technically, I was right that these stand-alone Pandora apps *should* be able to continue streaming rather than allowing OS X to sleep them. But to function in a logical way — to allow the user, not the OS, to decide when to stop streaming — the apps would need to be coded that way. And since they're apparently NOT coded to keep OS X from sleeping the wi-fi connection while they're running, the two choices are 1) Set sleep to "Never" in Energy Saver, or 2) visit the App Store and install the likes of "Wimoweh" or "Amphetamine" to selectively prevent apps like this — apps that need to keep the wi-fi from sleeping to function correctly — from going to sleep in the first place.

A 3rd and better option would be for the developers to address the obvious problem that they are building a streaming app and by definition the streaming shouldn't stop unless the user initiates that action. And so the 3rd option for those who find themselves frustrated by this limitation is to contact the app developer in question and suggest that they implement what is known in coding as an "Assertion". I'm not technical enough to pretend to understand it, so I'll quote the Wimoweh FAQ directly:

Shouldn’t applications / OS X being handling sleep already?


Yes they absolutely should. I first wrote Wimoweh to scratch an itch – I was fed up of coming back to find that my machine had gone to sleep when it should have been ripping a disc or encoding a file. As newer versions of OS X have made power management at the application level easier the problem should lessen. Handbrake for example now creates assertions when it’s working. If you’re using Wimoweh to stop the system sleeping to handle one specific app it might be worth asking the developer to check out IOPMAssertionCreateWithDescription in Apple’s developer documentation. In just a few lines of code they can have their application inform OS X when the application is busy and then you, in the best possible way, will no longer need to use Wimoweh. That being said Wimoweh makes it easy to do this kind of power management in one place and is particularly useful for command line, Java or Web applications that do not have visibility of OS X’s power management interfaces. Wimoweh also handles schedules, timers, can stay awake when your machine has been busy for a particularly amount of time or based on network activities none of which are available by default.

Source: http://www.serialangels.co.uk/index.php/appkiller-faqs/wimoweh-faq/

One of my pet peeves is searching Google to find help only to read a discussion for which the user who requested help never posts a follow-up to indicate what did or did not work. This last post to this topic is my attempt to make sure that others have fewer headaches (or at least more clues to what might be the problem). Even though I feel like I've been talking (mostly) to myself, LOL, I hope this helps someone else in some way. And so now the biggest question yet: Do I rate my own answer as "Helpful"? 😉

View in context
15 replies
Question marked as Top-ranking reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Jan 5, 2017 5:25 PM in response to NewsView

Final post to this topic for those who come along later in search of a solution to a similar issue:


I located Apple's official stance on sleeping a "portable". It explains why my experience with my MBP is so much different than what is normal on my iMac even though I'm running El Cap on both:


Portable computers have no network connectivity when in sleep mode, but can wake if the Energy Saver option "Wake for network access" is enabled. If you wish to use file sharing or don't want to interrupt your Internet connection, you should not manually put the computer to sleep, and you should drag the "Computer sleep" slider to Never.

Source: About Energy Saver sleep and idle modes in Mac OS X - Apple Support

Originally, there were two issues that prompted this topic: 1) Both Pandora apps I installed simply disconnected and stopped streaming. 2) Both crashed upon sleep/wake. Most — but not all — of the crashing stopped by removing a third-party audio driver (Soundflower). And yet with continued use I found that HD Radio for Pandora and Hermes were still experiencing a few too many crashes associated with the *normal behavior* of my MBP to disconnect from wi-fi on sleep.

My view on this from the outset was that it shouldn't be necessary to alter ALL Energy Saver sleep settings just to make one type of app work. It turns out that the developers may have dropped the ball on both the apps I have been using by not encoding the proper Assertions. So technically, I was right that these stand-alone Pandora apps *should* be able to continue streaming rather than allowing OS X to sleep them. But to function in a logical way — to allow the user, not the OS, to decide when to stop streaming — the apps would need to be coded that way. And since they're apparently NOT coded to keep OS X from sleeping the wi-fi connection while they're running, the two choices are 1) Set sleep to "Never" in Energy Saver, or 2) visit the App Store and install the likes of "Wimoweh" or "Amphetamine" to selectively prevent apps like this — apps that need to keep the wi-fi from sleeping to function correctly — from going to sleep in the first place.

A 3rd and better option would be for the developers to address the obvious problem that they are building a streaming app and by definition the streaming shouldn't stop unless the user initiates that action. And so the 3rd option for those who find themselves frustrated by this limitation is to contact the app developer in question and suggest that they implement what is known in coding as an "Assertion". I'm not technical enough to pretend to understand it, so I'll quote the Wimoweh FAQ directly:

Shouldn’t applications / OS X being handling sleep already?


Yes they absolutely should. I first wrote Wimoweh to scratch an itch – I was fed up of coming back to find that my machine had gone to sleep when it should have been ripping a disc or encoding a file. As newer versions of OS X have made power management at the application level easier the problem should lessen. Handbrake for example now creates assertions when it’s working. If you’re using Wimoweh to stop the system sleeping to handle one specific app it might be worth asking the developer to check out IOPMAssertionCreateWithDescription in Apple’s developer documentation. In just a few lines of code they can have their application inform OS X when the application is busy and then you, in the best possible way, will no longer need to use Wimoweh. That being said Wimoweh makes it easy to do this kind of power management in one place and is particularly useful for command line, Java or Web applications that do not have visibility of OS X’s power management interfaces. Wimoweh also handles schedules, timers, can stay awake when your machine has been busy for a particularly amount of time or based on network activities none of which are available by default.

Source: http://www.serialangels.co.uk/index.php/appkiller-faqs/wimoweh-faq/

One of my pet peeves is searching Google to find help only to read a discussion for which the user who requested help never posts a follow-up to indicate what did or did not work. This last post to this topic is my attempt to make sure that others have fewer headaches (or at least more clues to what might be the problem). Even though I feel like I've been talking (mostly) to myself, LOL, I hope this helps someone else in some way. And so now the biggest question yet: Do I rate my own answer as "Helpful"? 😉

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 31, 2016 7:33 PM in response to Eric Root

Thanks, Eric. I only purchased the McAfee Total Protection this month. I appreciate that antivirus software is known to slow down the computer down a bit but what is confusing is that on my iMac I have the same OS and the same Pandora apps running with this same McAfee product and no issues. Should I try uninstalling and reinstalling McAfee on my MacBook or are you recommending leaving it uninstalled permanently?


Thanks again for the reply & Happy New Year!

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 31, 2016 7:44 PM in response to Eric Root

Just looked at the resources on the page link, but the one that caught my attention "How to Unblock Things from McAfee" seems to suggest that apps can be adjusted with respect to McAfee/firewall settings. Since I didn't have to do any tinkering on the iMac with respect to McAfee/Pandora streaming it never occurred to me that it would be McAfee. But I'll continue checking into it. Thanks again!

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Jan 1, 2017 12:27 PM in response to Eric Root

Unfortunately, removing McAfee didn't resolve the Pandora crash issues.


I booted into Safe Mode to try to prompt some of the system preferences to be rebuilt. While in Safe Mode I ran Network Diagnostics in monitoring mode while streaming audio. I then put the Mac to sleep to trigger the disconnect while the monitoring was still active. At that point, HD Radio for Pandora crashed. Unfortunately, after generating the network diagnostic report it was difficult to make sense of the results. (To my eye, nothing specific/major was flagged by ND.) Next, I threw away some network plist/preferences and I also threw away a Power Management plist file. When the problem with crash-on-sleep still occurred after rebooting I also renewed the DHCP lease.


After taking the above steps HD Radio for Pandora gave me an actual error dialog box instead of just the System reporting that the app had crashed. I got one such error dialog with the Pandora app idle in the background after a disconnect, and the message amounted to the app requiring "an active internet connection" to stream. So this would seem to confirm that the crash is brought on by sleep. Upon acknowledging the message the audio streaming automatically picked back up. But when the MacBook went back to sleep again a few minutes later, the usual crash occurred (System offering to send report to Apple with no specific feedback from the Pandora app itself).


On my MacBook, in spite of having the Energy Saver pref box checked that says "wake for network access", the HD sleep settings will override the network connection even if it is in use at the time the MacBook enters sleep mode. In Snow Leopard, there are no sleep/wake or network timeout/crash issues with Hermes, and on that same iMac no problem in the El Cap partition running HD Radio for Pandora (same version as what is constantly crashing on the MacBook). So I am leaning toward the conclusion that the El Cap install was faulty and I'll need to start from scratch. Here's the thing, though: I can't be the only one in these forums streaming Pandora over a MacBook using a stand-alone app (not a web browser) to do so. So here are my questions:


Does everyone who uses a MacBook to stream Pandora find it necessary to disable HD sleep in Energy Saver as a means to do so successfully OR should I be able to have the wi-fi connection remain open to stream even if the balance of the system is in sleep mode? If the answer is, "No, you shouldn't have to disable MacBook sleep to stream audio", then what is the method for enabling TCP/IP "keep alive" under El Capitan (i.e. disable wi-fi sleep)?

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Jan 2, 2017 11:45 PM in response to Eric Root

Eric, I tried uninstalling McAfee and when that didn't help I reinstalled El Cap over the existing install. I am still seeing the same behavior from both "Hermes" and "HD Radio for Pandora", except now the latest wrinkle is that Hermes crashes without triggering any System popup/error at all (no option to "report" to Apple).


😟

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Jan 3, 2017 9:20 PM in response to Eric Root

@ Eric Are you busy/unavailable due to the recent holiday or do the crashlogs not offer up any clues?


Based on what's showing up in the latest crashlog would it do *any good* to totally wipe and reformat the hard drive and reinstall the OS from scratch (as opposed to the overlay-install I just did)?


I originally posted this under the El Cap forum and under the MacBook forum because I truly don't know if it is hardware or software acting up. And so for reference, I've condensed the most recent crashlog down to what seems to be the relevant portions.


Any follow up would be helpful (even if it's just to say it's not apparent what the problem is!):


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Exception Note: EXC_CORPSE_NOTIFY


…


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.audio.toolbox.AudioToolbox 0x00007fff995be285 MP3AudioStream::GeneratePackets(AudioFileStreamContinuation&) + 1527

1 com.apple.audio.toolbox.AudioToolbox 0x00007fff995a2630 AudioFileStreamObject::ParseBytes(unsigned int, AudioFileStreamContinuation&) + 108

2 com.apple.audio.toolbox.AudioToolbox 0x00007fff995a1ebf AudioFileStreamWrapper::ParseBytes(unsigned int, void const*, unsigned int) + 97


…


Thread 0 crashed with X86 Thread State (64-bit):

rax: 0xa00007fb3c8c4d69 rbx: 0x0000000000000688 rcx: 0x0000000000000000 rdx: 0x0000000000000688

rdi: 0x00007fb3c904c200 rsi: 0x0000000109908c5f rbp: 0x00007fff56326a80 rsp: 0x00007fff563269a0

r8: 0x0000000000000006 r9: 0x0000000000000000 r10: 0x00007fb3c983ba00 r11: 0x00000001099263a8

r12: 0x0000000000000688 r13: 0x0000000000000004 r14: 0x00007fb3c8ca03e0 r15: 0x00007fb3c8ca03e8

rip: 0x00007fff995be285 rfl: 0x0000000000010246 cr2: 0x0000000105462000


Logical CPU: 0

Error Code: 0x00000000

Trap Number: 13

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Jan 4, 2017 11:23 AM in response to NewsView

For the benefit of anyone who faces similar issues in the future dealing with these Pandora streaming apps on a MacBook, I am posting a follow up even though this thread has generated mostly crickets 😐: On "AskDifferent" a helpful user asked me to run a command line to check for third-party Audio components. The MBP in question was purchased used and the disk image used for the El Cap install contained a remanent of the Soundflower driver, which was responsible for crashing the apps (and because I didn't install it to begin with, I didn't know Soundflower wasn't supposed to be a part of my Sound preferences).


The good news is, no more spontaneous (constant) crashes! (Yay!) Bad news is, Hermes as of today is no longer maintaining a connection though wi-fi even when I'm actively using the computer. (So instead of dropping only during sleep, it reports an audio streaming failure every 2-3 minutes.) I have enough of a wi-fi connection to use my browser and post this reply but now I can't get Pandora to make it through a single track before disconnecting. (I'm hoping it's on their end and will spontaneously resolve but knowing my luck…😝)


The final aspect of today's update is that I attempted to make use of "Winoweh" and "Amphetamine" from the App Store. Neither of them are doing what they claim they can do, which is to allow the user to selectively override Energy Saver settings. Both were tried/configured to "keep awake" my MBP every time Hermes is running (and not to sleep the wi-fi). But no joy. 😠 And so I'm back to an undesirable solution of "never" for my sleep settings in Energy Saver (undesirable because I would prefer to preserve as much of the MacBook's battery as possible by allowing normal sleep function otherwise).


I am updating this topic in case anyone can provide additional insight into how to achieve a "keep alive" function for wi-fi while streaming Pandora from the likes of Hermes or HD Radio for Pandora. Meanwhile, because I continue to experience issues with apps not behaving the way they should — to include even the apps I downloaded to solve the sleep/disconnect issue — I'm open to advice as to whether or not I should just wipe this El Cap disk image and start over from scratch.

Reply
User profile for user: Eric Root
Eric Root
User level: Level 10
684,531 points

Dec 28, 2016 2:32 PM in response to NewsView

Try running this program in your normal account , then copy and paste the output in a reply. The program was created by Etresoft, a frequent contributor. Please use copy and paste as screen shots can be hard to read. On the screen with Options, please open Options and check the bottom 2 boxes before running. Click “Share Report” button in the toolbar, select “Copy to Clipboard” and then paste into a reply. This will show what is running on your computer. No personal information is shown.

Etrecheck – System Information

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 28, 2016 6:53 PM in response to Eric Root

Thanks for the reply, Eric.


I downloaded the app as recommended and chose as the problem "apps are crashing". At the time I ran the diagnostic I had Hermes in the trash and only HD Radio for Pandora still fully installed. Here is a C&P of what look to be the relevant parts:



Gatekeeper:ⓘ

Mac App Store and identified developers


Kernel Extensions:ⓘ

/Applications/Toast 15 Titanium/Toast Audio Assistant.app

[loaded] com.Cycling74.driver.Soundflower (1.6.7 - SDK 10.7 - 2016-12-09) [Support]


~/Library/Services/ToastIt.service/Contents/MacOS

[not loaded] com.roxio.TDIXController (2.0 - 2016-12-09) [Support]


System Launch Agents:ⓘ

[not loaded] 7 Apple tasks

[loaded] 156 Apple tasks

[running] 76 Apple tasks


System Launch Daemons:ⓘ

[failed] com.apple.Kerberos.kdc.plist (2016-07-08)

[not loaded] 45 Apple tasks

[loaded] 149 Apple tasks

[running] 95 Apple tasks


Launch Agents:ⓘ

[running] com.Monity.Helper.plist (2016-12-06) [Support]

[not loaded] com.adobe.AAM.Updater-1.0.plist (2016-12-09) [Support]

[running] com.mcafee.menulet.plist (2016-12-06) [Support]

[running] com.mcafee.reporter.plist (2016-12-06) [Support]


Launch Daemons:ⓘ

[loaded] com.adobe.SwitchBoard.plist (2016-12-08) [Support]

[running] com.adobe.agsservice.plist (2016-12-16) [Support]

[loaded] com.adobe.fpsaud.plist (2016-12-10) [Support]

[running] com.mcafee.cspd.plist (2016-03-15) [Support]

[not loaded] com.mcafee.ssm.ScanFactory.plist (2016-07-26) [Support]

[not loaded] com.mcafee.ssm.ScanManager.plist (2016-07-26) [Support]

[running] com.mcafee.virusscan.fmpd.plist (2016-03-29) [Support]

[loaded] com.microsoft.autoupdate.helper.plist (2016-12-13) [Support]

[loaded] com.microsoft.office.licensingV2.helper.plist (2016-06-11) [Support]


User Launch Agents:ⓘ

[loaded] com.adobe.AAM.Updater-1.0.plist (2016-12-07) [Support]


User Login Items:ⓘ

Flux Application

(/Applications/Flux.app)

gfxCardStatus Application

(~/Downloads/gfxCardStatus.app)

iTunesHelper Application (2016-12-14)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

TotalFinder Application

(/Applications/TotalFinder.app)

Hermes Application

(~/.Trash/Hermes.app)

Hermes Application

(~/.Trash/Hermes 11.42.44 PM.app)

OneDrive Launcher SMLoginItem (2016-12-27)

(/Applications/OneDrive.app/Contents/Library/LoginItems/OneDrive Launcher.app)

weatherbugosxhelper SMLoginItem (2016-12-05)

(/Applications/WeatherBug.app/Contents/Library/LoginItems/weatherbugosxhelper.a pp)

com.adobe.SwitchBoard.monitor.plist MachInit

(/etc/mach_init_per_user.d/com.adobe.SwitchBoard.monitor.plist)

Mach Init items are deprecated



Diagnostics Information:ⓘ

Dec 28, 2016, 01:37:55 AM ~/Library/Logs/DiagnosticReports/HD Radio for Pandora_2016-12-28-013755_[redacted].crash

com.anobot.Pandora - /Applications/HD Radio for Pandora.app/Contents/MacOS/HD Radio for Pandora

Dec 28, 2016, 12:34:59 AM ~/Library/Logs/DiagnosticReports/com.apple.preferences.sharing.remoteservice_20 16-12-28-003459_[redacted].crash

/System/Library/PreferencePanes/SharingPref.prefPane/Contents/XPCServices/com.a pple.preferences.sharing.remoteservice.xpc/Contents/MacOS/com.apple.preferences. sharing.remoteservice

Dec 28, 2016, 12:25:23 AM ~/Library/Logs/DiagnosticReports/HD Radio for Pandora_2016-12-28-002523_[redacted].crash

Dec 27, 2016, 09:27:22 PM Self test - passed



Does the information above help?


Thanks for the input (and apologies for the belated reply; I just now got home after posting this topic earlier today).

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 28, 2016 9:45 PM in response to Eric Root

Forgot to add the report says the hardware checks out, and condition is "excellent".


I accidentally omitted the Internet plug-ins/extensions so here they are:


Internet Plug-ins:ⓘ

AdobeExManDetect: AdobeExManDetect 1.1.0.0 - SDK 10.7 (2016-12-09) [Support]

FlashPlayer-10.6: 24.0.0.186 - SDK 10.9 (2016-12-20) [Support]

QuickTime Plugin: 7.7.3 (2016-12-14)

Flash Player: 24.0.0.186 - SDK 10.9 (2016-12-20) [Support]

AdobePDFViewer: 10.1.1 (2016-12-08) [Support]

Default Browser: 601 - SDK 10.11 (2016-12-05)

SiteAdvisor: 2.0 - SDK 10.1 (2014-12-05) [Support]

JavaAppletPlugin: 15.0.1 - SDK 10.7 (2016-12-16) Check version


Safari Extensions:ⓘ

Adblock Plus - Eyeo GmbH - https://adblockplus.org/ (2016-12-22)

SiteAdvisor - McAfee - http://www.siteadvisor.com (2016-12-06)


3rd Party Preference Panes:ⓘ

Flash Player (2016-12-10) [Support]


Diagnostics Information:ⓘ

Dec 28, 2016, 09:08:34 PM ~/Library/Logs/DiagnosticReports/HD Radio for Pandora_2016-12-28-210834_[redacted].crash

com.anobot.Pandora - /Applications/HD Radio for Pandora.app/Contents/MacOS/HD Radio for Pandora

Dec 28, 2016, 08:51:13 PM Self test - passed

Dec 28, 2016, 01:37:55 AM ~/Library/Logs/DiagnosticReports/HD Radio for Pandora_2016-12-28-013755_[redacted].crash

Dec 28, 2016, 12:34:59 AM ~/Library/Logs/DiagnosticReports/com.apple.preferences.sharing.remoteservice_20 16-12-28-003459_[redacted].crash

/System/Library/PreferencePanes/SharingPref.prefPane/Contents/XPCServices/com.a pple.preferences.sharing.remoteservice.xpc/Contents/MacOS/com.apple.preferences. sharing.remoteservice

Dec 28, 2016, 12:25:23 AM ~/Library/Logs/DiagnosticReports/HD Radio for Pandora_2016-12-28-002523_[redacted].crash

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 28, 2016 10:43 PM in response to NewsView

Here's my last update for the evening: I logged out of the Admin account and logged in as Guest and then ran the HD Radio for Pandora from there. I was able to reproduce the same problem. The Pandora app crashes at the end of the third song (about 7-10 minutes after launch). I'm not sure if there is some kind of disconnect-on-sleep that could be in play but why that should trigger a crash is another matter, regardless.

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 29, 2016 11:40 AM in response to Eric Root

Re: Eric: Were the reports I posted in any way useful?




In my most recent troubleshooting step I ran Apple Hardware Diagnostics (passed extended test) and I ran Disk Utility. The app is still crashing, unfortunately. I get maybe 7 minutes of playback on Hermes, about 12 on HD Radio for Pandora. It always crashes at the point where it is time to load a new song (after I walk away from the computer).


My next suspect to rule out is a network/energy saver timeout that is breaking the Pandora connection. Unfortunately, I need some pointers in this regard, too.


This issue is similar to what I experienced on an Android smartphone a few years ago where when the phone would sleep the Pandora audio connection would break. The problem is, I don't know how to specifically verify that my MacBook energy saver settings are configured to allow the Pandora connection to remain open (similar to what I had to do on my phone). In the Energy Saver preference pane I see the option to adjust screen sleep and HD sleep parameters but nothing specifically related to network connections for audio streaming.


Q: If I want to rule out crash-on-sleep issues the question would be, how do I set the MacBook to maintain an open network connection (to Pandora) but NOT adversely impact the energy saver settings system-wide?😕


Anybody else care to weigh in? I've been using Macs exclusively since the '80s and would have been considered a power user in the pre-OS X days but I'm of the belief now that if it's not broke, don't fix it. Snow Leopard was stable and thus it never gave me any occasion to learn troubleshooting skills on the order that is required now. (Which is both good and bad! :-)


To recap, I have other Macs on the same network that can successfully stream Pandora on the same OS over the same connection using the same app version numbers. Consequently, this would NOT appear to be a Pandora issue but something related to the MacBook itself. Either it's a network/sleep issue, an El Cap system clash with an app or something in the OS is corrupted and I will have to reinstall the OS. But reinstalling the OS is a last resort, hence I'm here hoping to get some help.


I will be stepping out for a couple hours shortly so if I don't respond right away it doesn't mean I won't be back to apply some of the solutions & thank those of you who jump in to offer assistance. Again, much appreciation for the help!

Reply
User profile for user: NewsView
NewsView Author
User level: Level 1
35 points

Dec 30, 2016 10:33 PM in response to NewsView

Okay, it looks like I narrowed it down: I found that if I prevent the hard drive from sleeping I can keep Pandora streaming and in so doing prevent the app from crashing. Since it is a MacBook and I do run it on battery and I would prefer not to prevent HD sleep entirely, so here's the follow up question: Is there a setting elsewhere in the network or energy saver prefs that can keep the network connection open without totally disabling HD sleep?


Anybody care to (kindly) jump in here now that it would appear the problem with both apps is sleep related? For example, any idea whether it is *normal* to have to prevent the HD from sleeping to stream Pandora to a MacBook? This MacBook is new to me (though not new) so I'm not on familiar ground with the hardware or the OS (having come to El Cap from Snow Leopard with none of the intermediary updates).

Reply

Two Different Pandora Apps Hang on MacBook (Crashlog Help)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up