The question why do MacBook Pro/Air, iMac, and Mac mini permanently crash pops up on the Apple support community pretty often. Very few Mac users manage to keep calm when a ‘spinning beach ball of death' appears on their Mac's screen. Even worse, macOS Sierra/High Sierra can get stuck on the ‘grey screen of death' after routine updates. In spite of having a bulletproof reputation, Macs do freeze and crash sometimes, so you have to know how to handle these issues. Read on to learn step-by-step troubleshooting instructions for all possible situations.
- Visual Studio For Mac Keeps Crashing On Mac Mini Version
- Visual Studio For Mac Keeps Crashing On Mac Mini Mac
- Visual Studio For Mac Keeps Crashing On Mac Mini 2
- Visual Studio For Mac Keeps Crashing On Mac Mini Windows 10
Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on screen. Open the Terminal (Applications Utilities Terminal). In the Terminal window, type in csrutil enable -without kext (or to fully disable: csrutil disable) and press Enter. Restart your Mac. Please share this page. I am using Visual Studio for Mac Community, version 7.3.3 (build 17) on Mac OSX 10.13.3. I am continually getting issues with Visual Studio hanging (becoming unresponsive) or outright crashing. I have performed a full uninstall and reinstall and am still facing the issue. For others who met similar crashes: you should check OS X crash log (in Console app) to see what exactly is the call stack. That either shows a hint on what might be the cause (when the solution in this thread did not help), or gives you something to report to Visual Studio Code guys. – Lex Li Dec 19 '15 at 7:01. When Microsoft Office 365 application keeps crashing, we often face some issues like freezing in safe mode and crashing on startup. There could be three possible situations when it keeps crashing: While working it stops responding. When you are not using it actively. During the startup of the application. When configured with Outlook application.
Macs can crash for a variety of reasons, which is why each particular situation needs separate troubleshooting activities. However, the typical reasons causing Mac crashes are as follows:
Malware/virus infection which infiltrated a Mac through third-party apps;
Insufficient RAM for applications to run properly;
Insufficient CPU capacity for resource-intensive programs; Free vpn for mac.
Several apps are competing for disk access and system resources.
How to fix the Finder app that keeps crashing on your Mac? The best option is deleting potentially corrupted Finder system preference files with .plist extension:
- If the Finder app still launches in spite of crashing, open the Finder window.
- Go to Home -> Library -> Preferences.
- Find and remove these files:apple.finder.plist and com.apple.sidebarlists.plist.
- Log out, and log back in.
- Empty the Trash.
Alternatively, you can use the Terminal app to remove the files, if Finder won't launch.
- Run the following commands:
rm ~/Library/Preferences/com.apple.finder.plist, then press Return.
rm ~/Library/Preferences/com.apple.sidebarlists.plist, then press Return.
- Log out, and log back in.
- Empty the Trash.
One of the most frequent issues with MacBook Pro is related to random crashes known as ‘kernel panic.' These crashes may occur after hardware replacement or software updates. To identify what's causing the problem, run Apple Diagnostics (or, Apple hardware test on Macs manufactured before 2013).
1.Unplug all external devices (keep the keyboard, mouse, monitor, Ethernet connection, and AC power plugged). Apple Hardware Test might show an error message if other devices are not unplugged.
2. Turn off your Mac, and turn it on again holding the D key while it is booting. Wait until the Apple Diagnostics screen (Apple Hardware Test icon) shows up:
3. If you're running the Apple Hardware Test, choose the language by pressing the ‘up' and ‘down' arrows, then hit the Return key to confirm. Apple Diagnostics performs the further steps automatically.
4. Next, click the Test button (T key) or Return to begin testing. Running an in-depth test needs a bit more time to complete. Select Perform extended testing before the test begins.
5. Once the test is over, you can see the results in the bottom-right part of the window.
6. To exit the diagnostics, click Restart (R key)/ Shut Down (S key) in the lower part of the window.
'A Mac update crashed my computer!' is another frequent plea for help on the Apple support community. Users know that installing Mac OS /software updates is the best way to keep their Mac protected. Still, many users have experienced crashes in the middle of a system upgrade. On older Mac models, upgrading to macOS Sierra on top of OS X El Capitan caused slow work and freeze ups. To fix the issues caused by upgrading to the latest Mac OS, you can do the following:
restart your Mac in a Safe Mode and disable the antivirus software (especially if you're using third-party antivirus software);
Visual Studio For Mac Keeps Crashing On Mac Mini Version
switch to another Wi-Fi network
try downgrading to the previous Mac OS version
perform a clean install of the new operating system
If your Mac crashed during the automatic software update, find and delete the following files:
- /Library/Preferences/com.apple.SoftwareUpdate.plist
- /Home/Library/Preferences/ByHost/com.apple.SoftwareUpdate.xyz.plist ('xyz' is a number).
- /Home/Library/Caches/com.apple.SoftwareUpdate/ (purge the entire folder).
Alternatively, use a Time Machine backup to revert to the previous state.
If you use one of the earlier Mac OS X versions, follow the below instructions to fix freeze-ups and system crashes. Choose an option depending on the severity of the problem:
- Try rebooting your Mac in a Safe Mode. For this, hold down the Shift key while restarting your computer until the Apple logo appears. If the startup fails, most likely you don't have enough free space on your startup disk.
- Try resetting the NVRAM. For this, restart your Mac and press down the Command-Option-P-R keys altogether after hearing the start-up chime. Release the keys after you hear the startup chime for the second time.
- Boot into the Recovery Mode. For this, restart your Mac holding down the Command (⌘)-R key combination after hearing the start-up sound. Check your hard drive for errors using the Disk Utility.
- If the problem persists, reinstalling Mac OS X from scratch is your best option. First, reboot your computer into the Recovery Mode. In the OS X Utilities menu, select Reinstall OS X, then click Continue.
Note: reinstalling OS X on top of the current system does not delete your files and settings. However, this may help in fixing some system-wide issues.
If your Mac crashes several times in a row, it is crucial to single out the problem. Find out if a particular application is a reason, or the entire operating system is affected. In the first case, you will get an application crash report with comments. To fix the issue, click Reopen to relaunch the app, or click OK to quit the alert window.
If the problem stems from the macOS itself, there can be a plethora of reasons causing it. Try the below steps to eliminate the issue:
- Reset the SMC (System Management Controller). Unplug all accessories before resetting. Press and hold down the Power button for 10 seconds to turn off your Mac. Disconnect the AC adapter and wait 15 seconds, then plug the power cord back in and switch on your Mac in 5 seconds.
- Reboot in Safe Mode. Restart your Mac while pressing down the Shift key after you hear the start-up chime.
- Reset NVRAM/PRAM. Restart Mac while holding down the Command-Option-P-R key combination.
- Uninstall third-party apps, plug-ins, antivirus software, PPTP VPN software, which may be incompatible with the current macOS version.
- Clean up your Mac's startup disk to ensure there is enough space for macOS to operate properly.
Mac crashes can stem from different reasons, which signal about serious application or system-related issues. Isolating and identifying the problem is the best way to single out all possible causes. To prevent your Mac from occasional freeze-ups and crashes, use the latest Mac OS and software compatible with your machine's hardware. macOS High Sierra is the recommended version of the operating system to date. Upgrade to the latest stable version to maximize your macOS experience.
-->In this section, you'll find solutions to common issues with Visual Studio Tools for Unity, descriptions of known issues, and learn how you can help improve Visual Studio Tools for Unity by reporting errors.
Troubleshooting the connection between Unity and Visual Studio
Confirm Editor Attaching is enabled
In the Unity Menu, select Edit > Preferences and then select the External Tools tab. Confirm that the Editor Attaching checkbox is enabled. For more information, see the Unity Preferences documentation.
Unable to attach
- Try to temporarily disable your antivirus or create exclusion rules for both VS and Unity.
- Try to temporarily disable your firewall or create rules for allowing TCP/UDP networking between VS and Unity.
- Some programs, like Team Viewer, can interfere with process detection. You can try to temporarily stop any extra software to see if it changes something.
- Do not rename the main Unity executable, as VSTU is only monitoring 'Unity.exe' processes.
Visual Studio crashes
This issue can be due to the Visual Studio MEF cache being corrupted.
Try removing the following folder to reset the MEF cache (close Visual Studio before doing this):
This should fix your issue. In case you are still experiencing the problem, run a Developer Command Prompt for Visual Studio as Administrator and use the following command:
Visual Studio stops responding
Several Unity plugins like Parse, FMOD, UMP (Universal Media Player), ZFBrowser, or Embedded Browser are using native threads. It's an issue when a plugin ends up attaching a native thread to the runtime, which then does blocking calls to the OS. This means Unity can't interrupt that thread for the debugger (or domain reload) and stop responding.
For FMOD, there is a workaround, you can pass FMOD_STUDIO_INIT_SYNCHRONOUS_UPDATE
initialization flag to disable asynchronous processing and perform all processing on the main thread.
Incompatible project in Visual Studio
First, check that Visual Studio is set as your external script editor in Unity (Edit/Preferences/External Tools). Then check that the Visual Studio plugin is installed in Unity (Help/About must display a message like Microsoft Visual Studio Tools for Unity is enabled at the bottom). Then check that the extension is properly installed in Visual Studio (Help/About).
Extra reloads, or Visual Studio losing all open windows
Be sure to never touch project files directly from an asset processor or any other tool. If you really need to manipulate the project file, we expose an API for that. Please check the Assembly references issues section.
If you experience extra reloads or if Visual Studio is losing all open Windows on reload, make sure that you have proper .NET targeting packs installed. Check the following section about frameworks for more information.
The debugger does not break on exceptions
When using the legacy Unity runtime (.NET 3.5 equivalent), the debugger will always break when an exception is unhandled (=outside a try/catch block). If the exception is handled, the debugger will use the Exception Settings Window to determine if a break is required or not.
With the new runtime (.NET 4.6 equivalent), Unity introduced a new way for managing user exceptions and as a result, all exceptions are seen as 'user-handled' even if they are outside a try/catch block. That's why you now need to explicitly check them in the Exception Settings Window if you want the debugger to break.
In the Exception Settings window (Debug > Windows > Exception Settings), expand the node for a category of exceptions (for example, Common Language Runtime Exceptions, meaning .NET exceptions), and select the check box for the specific exception you want to catch within that category (for example System.NullReferenceException). You can also select an entire category of exceptions.
On Windows, Visual Studio asks to download the Unity target framework
Visual Studio Tools for Unity requires the .NET framework 3.5, which isn't installed by default on Windows 8 or 10. To fix this issue, follow the instructions to download and install the .NET framework 3.5.
When using the new Unity runtime, .NET targeting packs version 4.6 and 4.7.1 are also required. It is possible to use the VS2017 installer to quickly install them (modify your VS2017 installation, individual components, .NET category, select all 4.x targeting packs).
Assembly reference issues
If your project is complex reference-wise or if you want to better control this generation step, you can use our API for manipulating the generated project or solution content. You can also use response files in your Unity project and we'll process them.
Breakpoints with a warning
If Visual Studio is unable to find a source location for a specific breakpoint you will see a warning around your breakpoint. Check that the script you are using is properly loaded/used in the current Unity scene.
Breakpoints not hit
Check that the script you are using is properly loaded/used in the current Unity scene. Quit both Visual Studio and Unity then delete all generated files (*.csproj, *.sln) and the whole Library folder.
switch to another Wi-Fi network
try downgrading to the previous Mac OS version
perform a clean install of the new operating system
If your Mac crashed during the automatic software update, find and delete the following files:
- /Library/Preferences/com.apple.SoftwareUpdate.plist
- /Home/Library/Preferences/ByHost/com.apple.SoftwareUpdate.xyz.plist ('xyz' is a number).
- /Home/Library/Caches/com.apple.SoftwareUpdate/ (purge the entire folder).
Alternatively, use a Time Machine backup to revert to the previous state.
If you use one of the earlier Mac OS X versions, follow the below instructions to fix freeze-ups and system crashes. Choose an option depending on the severity of the problem:
- Try rebooting your Mac in a Safe Mode. For this, hold down the Shift key while restarting your computer until the Apple logo appears. If the startup fails, most likely you don't have enough free space on your startup disk.
- Try resetting the NVRAM. For this, restart your Mac and press down the Command-Option-P-R keys altogether after hearing the start-up chime. Release the keys after you hear the startup chime for the second time.
- Boot into the Recovery Mode. For this, restart your Mac holding down the Command (⌘)-R key combination after hearing the start-up sound. Check your hard drive for errors using the Disk Utility.
- If the problem persists, reinstalling Mac OS X from scratch is your best option. First, reboot your computer into the Recovery Mode. In the OS X Utilities menu, select Reinstall OS X, then click Continue.
Note: reinstalling OS X on top of the current system does not delete your files and settings. However, this may help in fixing some system-wide issues.
If your Mac crashes several times in a row, it is crucial to single out the problem. Find out if a particular application is a reason, or the entire operating system is affected. In the first case, you will get an application crash report with comments. To fix the issue, click Reopen to relaunch the app, or click OK to quit the alert window.
If the problem stems from the macOS itself, there can be a plethora of reasons causing it. Try the below steps to eliminate the issue:
- Reset the SMC (System Management Controller). Unplug all accessories before resetting. Press and hold down the Power button for 10 seconds to turn off your Mac. Disconnect the AC adapter and wait 15 seconds, then plug the power cord back in and switch on your Mac in 5 seconds.
- Reboot in Safe Mode. Restart your Mac while pressing down the Shift key after you hear the start-up chime.
- Reset NVRAM/PRAM. Restart Mac while holding down the Command-Option-P-R key combination.
- Uninstall third-party apps, plug-ins, antivirus software, PPTP VPN software, which may be incompatible with the current macOS version.
- Clean up your Mac's startup disk to ensure there is enough space for macOS to operate properly.
Mac crashes can stem from different reasons, which signal about serious application or system-related issues. Isolating and identifying the problem is the best way to single out all possible causes. To prevent your Mac from occasional freeze-ups and crashes, use the latest Mac OS and software compatible with your machine's hardware. macOS High Sierra is the recommended version of the operating system to date. Upgrade to the latest stable version to maximize your macOS experience.
-->In this section, you'll find solutions to common issues with Visual Studio Tools for Unity, descriptions of known issues, and learn how you can help improve Visual Studio Tools for Unity by reporting errors.
Troubleshooting the connection between Unity and Visual Studio
Confirm Editor Attaching is enabled
In the Unity Menu, select Edit > Preferences and then select the External Tools tab. Confirm that the Editor Attaching checkbox is enabled. For more information, see the Unity Preferences documentation.
Unable to attach
- Try to temporarily disable your antivirus or create exclusion rules for both VS and Unity.
- Try to temporarily disable your firewall or create rules for allowing TCP/UDP networking between VS and Unity.
- Some programs, like Team Viewer, can interfere with process detection. You can try to temporarily stop any extra software to see if it changes something.
- Do not rename the main Unity executable, as VSTU is only monitoring 'Unity.exe' processes.
Visual Studio crashes
This issue can be due to the Visual Studio MEF cache being corrupted.
Try removing the following folder to reset the MEF cache (close Visual Studio before doing this):
This should fix your issue. In case you are still experiencing the problem, run a Developer Command Prompt for Visual Studio as Administrator and use the following command:
Visual Studio stops responding
Several Unity plugins like Parse, FMOD, UMP (Universal Media Player), ZFBrowser, or Embedded Browser are using native threads. It's an issue when a plugin ends up attaching a native thread to the runtime, which then does blocking calls to the OS. This means Unity can't interrupt that thread for the debugger (or domain reload) and stop responding.
For FMOD, there is a workaround, you can pass FMOD_STUDIO_INIT_SYNCHRONOUS_UPDATE
initialization flag to disable asynchronous processing and perform all processing on the main thread.
Incompatible project in Visual Studio
First, check that Visual Studio is set as your external script editor in Unity (Edit/Preferences/External Tools). Then check that the Visual Studio plugin is installed in Unity (Help/About must display a message like Microsoft Visual Studio Tools for Unity is enabled at the bottom). Then check that the extension is properly installed in Visual Studio (Help/About).
Extra reloads, or Visual Studio losing all open windows
Be sure to never touch project files directly from an asset processor or any other tool. If you really need to manipulate the project file, we expose an API for that. Please check the Assembly references issues section.
If you experience extra reloads or if Visual Studio is losing all open Windows on reload, make sure that you have proper .NET targeting packs installed. Check the following section about frameworks for more information.
The debugger does not break on exceptions
When using the legacy Unity runtime (.NET 3.5 equivalent), the debugger will always break when an exception is unhandled (=outside a try/catch block). If the exception is handled, the debugger will use the Exception Settings Window to determine if a break is required or not.
With the new runtime (.NET 4.6 equivalent), Unity introduced a new way for managing user exceptions and as a result, all exceptions are seen as 'user-handled' even if they are outside a try/catch block. That's why you now need to explicitly check them in the Exception Settings Window if you want the debugger to break.
In the Exception Settings window (Debug > Windows > Exception Settings), expand the node for a category of exceptions (for example, Common Language Runtime Exceptions, meaning .NET exceptions), and select the check box for the specific exception you want to catch within that category (for example System.NullReferenceException). You can also select an entire category of exceptions.
On Windows, Visual Studio asks to download the Unity target framework
Visual Studio Tools for Unity requires the .NET framework 3.5, which isn't installed by default on Windows 8 or 10. To fix this issue, follow the instructions to download and install the .NET framework 3.5.
When using the new Unity runtime, .NET targeting packs version 4.6 and 4.7.1 are also required. It is possible to use the VS2017 installer to quickly install them (modify your VS2017 installation, individual components, .NET category, select all 4.x targeting packs).
Assembly reference issues
If your project is complex reference-wise or if you want to better control this generation step, you can use our API for manipulating the generated project or solution content. You can also use response files in your Unity project and we'll process them.
Breakpoints with a warning
If Visual Studio is unable to find a source location for a specific breakpoint you will see a warning around your breakpoint. Check that the script you are using is properly loaded/used in the current Unity scene.
Breakpoints not hit
Check that the script you are using is properly loaded/used in the current Unity scene. Quit both Visual Studio and Unity then delete all generated files (*.csproj, *.sln) and the whole Library folder.
Unable to debug Android players
We use multicast for player detection (which is the default mechanism used by Unity), but after that we use a regular TCP connection to attach the debugger. The detection phase is the main issue for Android devices.
Wifi is versatile but super slow compared to USB because of latency. We saw a lack of proper multicast support for some routers or devices (Nexus series are well known for this).
Visual Studio For Mac Keeps Crashing On Mac Mini Mac
USB is super-fast for debugging, and Visual Studio Tools for Unity is now able to detect USB devices, and talk to the adb server to properly forward ports for debugging.
Issues with Visual Studio 2015 and IntelliSense or code coloration
Try upgrading your Visual Studio 2015 to update 3.
Visual Studio For Mac Keeps Crashing On Mac Mini 2
Known issues
There are known issues in Visual Studio Tools for Unity that result from how the debugger interacts with Unity's older version of the C# compiler. We're working to help fix these problems, but you might experience the following issues in the meantime:
When debugging, Unity sometimes crashes.
When debugging, Unity sometimes freezes.
Stepping into and out of methods sometimes behaves incorrectly, especially in iterators or within switch statements.
Report errors
Please help us improve the quality of Visual Studio Tools for Unity by sending error reports when you experience crashing, freezes, or other errors. This helps us investigate and fix problems in Visual Studio Tools for Unity. Thank you!
How to report an error when Visual Studio freezes
There are reports that Visual Studio sometimes freezes when debugging with Visual Studio Tools for Unity, but we need more data to understand this problem. You can help us investigate by following the steps below.
To report that Visual Studio freezes while debugging with Visual Studio Tools for Unity
On Windows:
Open a new instance of Visual Studio.
Mesh enabler 2019. Open the Attach to Process dialog. In the new instance of Visual Studio, on the main menu, choose Debug, Attach to Process.
Attach the debugger to the frozen instance of Visual Studio. In the Attach to Process dialog, select the frozen instance of Visual Studio from the Available Processes table, then choose the Attach button.
Pause the Debugger. In the new instance of Visual Studio, on the main menu, choose Debug, Break All, or just press Ctrl+Alt+Break.
Create a thread-dump. In the Command window, enter the following command and press Enter:
You might need to make the Command window visible first. In Visual Studio, on the main menu, choose View, Other Windows, Command Window.
On Mac:
Open a terminal and get the PID of Visual Studio for Mac:
Launch the lldb debugger:
Attach to the Visual Studio for Mac instance using the PID:
Retrieve the stacktrace for all the threads:
Visual Studio For Mac Keeps Crashing On Mac Mini Windows 10
Finally, send the thread-dump to vstusp@microsoft.com, along with a description of what you were doing when Visual Studio became frozen. Install curl mac os.