OS X Live assertion failed libxpc.dylib Flooding breach
Posted: Mon Jan 04, 2016 1:30 am
Calling all Ableton Live MAC OS X El Capitan users who are experiencing unsolved flooding on their console with the following message or similar:
1/3/16 4:12:00.762 PM Live[771]: assertion failed: XXXXX: libxpc.dylib + XXXXX [XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX]: XxXX
You must have correctly installed The Latest Live, Max, And Java packages and those three must be running with no problems.
I noticed my system behaving erratically so I opened the console and I noticed weird system responses. Before I could investigate further or keep monitoring the output, the console started getting flooded with the above-mentioned message. There is possible increase of battery usage, memory leaks and I am also considering networking issues since I noticed an exception was added to my firewall from the MAX application, which uses Java. This may be part of the functionality, but I'm still considering networking as a probable cause for this problem.
Disconnecting the internet, resetting Live settings, disabling plugins, reinstalling and reauthorizing, disabling wifi and internet access, disconnecting peripheral devices, resetting NVRAM and repairing disk permissions doesn't help. We are starting to investigate this problem in depth. Please try these things before posting.
Just opening the program, letting it sit there, and waiting for about ten minutes triggers this problem without adding tracks, sounds, or devices, or even touching the Live application.
I have sent a message to Ableton about this problem and we are currently working on this issue, but I would like anyone who is experiencing the same problem to post here so that we can help Ableton find a solution. My friends from Ableton mentioned they haven't had that many user reports on this problem so I thought I'd help by posting to see how many people are having this issue and find as much information for them to use. The following forum posts are related to this problem:
viewtopic.php?f=1&t=217381&p=1680976#p1680976
https://discussions.apple.com/thread/6822693
viewtopic.php?f=1&t=217747&p=1676149&hi ... b#p1676149
The only user-provided solution so far is a complete MAC OS X system reinstall, which is out of the question for most of us who have hundreds of gigabytes in sounds saved into our hard drives and reinstalling would take too much time, when this problem could be solved instead if we all help.
Thanks very much in advance.
1/3/16 4:12:00.762 PM Live[771]: assertion failed: XXXXX: libxpc.dylib + XXXXX [XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX]: XxXX
You must have correctly installed The Latest Live, Max, And Java packages and those three must be running with no problems.
I noticed my system behaving erratically so I opened the console and I noticed weird system responses. Before I could investigate further or keep monitoring the output, the console started getting flooded with the above-mentioned message. There is possible increase of battery usage, memory leaks and I am also considering networking issues since I noticed an exception was added to my firewall from the MAX application, which uses Java. This may be part of the functionality, but I'm still considering networking as a probable cause for this problem.
Disconnecting the internet, resetting Live settings, disabling plugins, reinstalling and reauthorizing, disabling wifi and internet access, disconnecting peripheral devices, resetting NVRAM and repairing disk permissions doesn't help. We are starting to investigate this problem in depth. Please try these things before posting.
Just opening the program, letting it sit there, and waiting for about ten minutes triggers this problem without adding tracks, sounds, or devices, or even touching the Live application.
I have sent a message to Ableton about this problem and we are currently working on this issue, but I would like anyone who is experiencing the same problem to post here so that we can help Ableton find a solution. My friends from Ableton mentioned they haven't had that many user reports on this problem so I thought I'd help by posting to see how many people are having this issue and find as much information for them to use. The following forum posts are related to this problem:
viewtopic.php?f=1&t=217381&p=1680976#p1680976
https://discussions.apple.com/thread/6822693
viewtopic.php?f=1&t=217747&p=1676149&hi ... b#p1676149
The only user-provided solution so far is a complete MAC OS X system reinstall, which is out of the question for most of us who have hundreds of gigabytes in sounds saved into our hard drives and reinstalling would take too much time, when this problem could be solved instead if we all help.
Thanks very much in advance.