Hello Charles I have emailed John Daniel but he has not responded. My apologies for the delay in responding to you. I've been on a road trip to Somerset. Sincerely David

I'm left wondering WHY a chap like you would be sending emails to John Daniel. Interestingly, you sound just like him!

Here is my profile information from 'over there'! https://discussions.apple.com/profile/HunterBD/participation

As everyone can read for themselves, I worked very hard to help answer questions on the ASC forums from less knowledgeable folk:-  hxxps://discussions.apple.com/profile/HunterBD/participation  Which of these many posts do you think could have been responsible for my lifetime ban from the ASC forums?  Here's a listing of posts I made. Perhaps you'd like to pick out one or two possibilities?  hxxps://discussions.apple.com/search?page=1&content=filterDiscussions&q=HunterBD&perPage=60  What was the final straw, as it were?  --  David

Thanks Claude ...... but WHY? And why is there no mention of it under 'My Activity'?

Hello again! 🙂 I'm wondering why the response by 'Purbeckview' is not recorded here:- https://developer.apple.com/forums/profile/Purbeckview%20?view=replies I'm also wondering why the post at the link I mentioned has been removed ....... https://developer.apple.com/forums/thread/705250 Have YOU any thoughts on these points? There is always a reason ...... for everything! Thanks.

Hello again! I'd be most grateful if someone would spare a few minutes to take a screenshot of what THEY see if they visit this thread:- https://discussions.apple.com/profile/HunterBD/participation I'd be even more grateful if they then share that screenshot here in this thread. Any volunteers? I do hope so!

Here's a screenshot taken by my friend!

Snit's response is NOT an "Accepted" reply! I'm keen to discover why there have been no other responses. Can you, will you, help? Thanks.

The phenomenon you're describing, where the "net.inet.udp.pcbcount" value significantly increases after closing the lid of a MacBook Pro and waiting for a while before reopening it, can indeed be indicative of a UDP (User Datagram Protocol) PCB (Protocol Control Block) leak. PCBs are data structures used by the operating system to manage network connections. When a UDP connection is established, a PCB is created to store information about that connection. However, if the PCB is not properly released or closed when the connection is terminated, it can lead to a resource leak. In this case, it appears that the number of UDP PCBs keeps increasing every time you close and reopen the lid of your MacBook Pro. The increasing number of UDP PCBs can lead to higher CPU usage and increased CPU temperature because the system needs to maintain and manage all these active connections. As the number of PCBs continues to rise, it consumes more system resources and can impact overall performance. To address this issue, you can try the following steps: Check for software updates: Make sure your MacBook Pro is running the latest version of macOS and has all the latest updates installed. Apple often releases software updates to address known issues and bugs. Restart your MacBook Pro: A simple restart can help clear any temporary system glitches and potentially release any lingering UDP PCBs. Reset network settings: Go to "System Preferences" > "Network" and select your network connection (Wi-Fi or Ethernet). Click on the "Advanced" button and then choose the "TCP/IP" tab. From there, click on the "Renew DHCP Lease" button and then "OK" to apply the changes. This will reset your network settings and may help resolve the issue. Check for rogue applications or processes: It's possible that a specific application or process is causing the UDP PCB leak. Monitor your system's activity using the "Activity Monitor" application (located in the "Utilities" folder within the "Applications" folder) and look for any processes or applications that may be consuming a large number of UDP PCBs. If you identify any suspicious processes, try updating or uninstalling the corresponding application. Contact Apple Support: If the issue persists and none of the above steps resolve the problem, it's recommended to reach out to Apple Support or visit an Apple Authorized Service Provider for further assistance. They can help diagnose the issue and provide specific troubleshooting steps or repair options. Remember to back up your important data regularly to ensure you don't lose any information in case further troubleshooting or repairs are required. I hope this helps!

Based on the provided crash report, it appears that Logic Pro X is crashing while playing a specific project. The crash is related to a bus error (SIGBUS) at a specific memory address. Here are some key details from the report: Process: Logic Pro X Version: 10.7.2 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE Crashed Thread: 0 (main thread) Unfortunately, the crash report does not provide specific information about the cause of the crash. However, it seems to be related to an effect rack or audio unit processing. The crash occurs at a memory address that is not accessible, which could indicate a memory issue or a problem with a specific audio effect. To troubleshoot and resolve the issue, you can try the following steps: Update Logic Pro X: Make sure you have the latest version of Logic Pro X installed. Check for any available updates in the Mac App Store. Disable third-party plugins: If you are using any third-party plugins or audio effects in your project, try removing or disabling them temporarily to see if the crash still occurs. Faulty or incompatible plugins can sometimes cause crashes in audio applications. Reset Logic Pro X preferences: Corrupted preferences can also cause crashes. Resetting Logic Pro X preferences to their default settings may help resolve the issue. To do this, quit Logic Pro X, then hold down the Option key and click on the Logic Pro X icon to open the Preferences dialog. Choose "Reset All Preferences" and restart Logic Pro X. Test with a new project: Create a new project in Logic Pro X and test if the crash occurs. If the crash only happens with a specific project, there may be an issue with that particular project file. You can try creating a new project and importing the tracks or settings from the problematic project. Contact Apple Support: If the issue persists and you are unable to resolve it, it's recommended to contact Apple Support for further assistance. They can provide more specific guidance based on the crash report and help troubleshoot the problem. Note: It's always a good idea to regularly save your work and backup important files to prevent data loss in case of crashes or other issues. = I hope this helps!

Hello again! I understand your frustration with the issue you're experiencing on your Mac and your desire for a solution that doesn't require frequent restarts. Perhaps I can provide some additional suggestions and information that might be helpful. Check Activity Monitor: Launch the Activity Monitor utility (you can find it in the Utilities folder within the Applications folder) and select the "CPU" tab. Look for any processes that are consuming a significant amount of CPU resources. If you notice any particular process causing high CPU usage, you can investigate further or consider uninstalling that application. Update macOS and Apps: Make sure you're running the latest version of macOS and that all your applications are up to date. Software updates often include bug fixes and performance improvements that could help resolve the issue you're experiencing. Reset SMC and NVRAM: Resetting the System Management Controller (SMC) and NVRAM (non-volatile random-access memory) on your Mac can sometimes help with performance issues and overheating problems. Instructions for resetting the SMC and NVRAM can be found on Apple's support website or by searching online for your specific Mac model. Check for Malware: Occasionally, malware or unwanted applications can cause high CPU usage and overheating. Consider running a thorough scan with reliable antivirus software to check for any malicious programs on your Mac. Seek Apple Support: If the issue persists and you've exhausted all troubleshooting options, it may be beneficial to reach out to Apple Support directly. They have specialized knowledge and resources to assist with macOS-related issues and can provide specific guidance based on your situation. Remember to provide detailed information about the problem, including any specific error messages, the steps you've already taken to troubleshoot, and the exact model and specifications of your Mac. This will help Apple Support better understand your situation and provide appropriate assistance. While these suggestions may not directly address the underlying cause of the issue you're experiencing, they can help mitigate the problem until a more permanent solution is found. Please let me know if these comments prove helpful.

My last post here has been removed. Will you respond if I email you, "eskimo"? Please advise.

Thank you, Eskimo! 🙂

"macOS is currently in need of substantial improvement to its usability, and a return to simple, consistent behaviours that conform to explicit and generally understood rules. That need not involve abandoning the great achievements of the SSV, Gatekeeper, or launch constraints, but improvements in their presentation using human factors."