(likely final) update: I'm convinced this is an issue with VS Code. Summary: Ubuntu completely freezes at seemingly random times, leaving no trace in logs, and is not related to any specific desktop environment or GNOME extensions. Yet another update! - Even with all GNOME extensions disabled, it still crashed. I don't know if this is related, but sometimes (and especially after booting) programs take a significant amount of time (> 5-10 seconds), even command line programs.
Update: The system logs show no indication of anything at all happening, let alone something wrong. I'm currently using the open source driver.Īll that I typically have open is Firefox (not a ton of tabs loaded) and VS Code, with at most a couple files and a terminal open. I was originally using the open source nVidia driver, and switched to the proprietary to no avail. I have attempted to switch graphics drivers, on the theory that it may be that. Every time, I must resort to SysRq + R E I S U B, which is (obviously) not preferred. Naturally, I have tried switching to a TTY session with no success. I cannot move the cursor or use the keyboard. Recently, under 17.10 and 18.04 (I just upgraded today), Ubuntu will randomly and completely freeze. I don't believe this is an issue related to Ubuntu, but rather VS Code. Just highlight an app from the list, click the X button in the upper-left corner, and then choose Quit or Force Quit.Please read: See the last bit. You can also use the Activity Monitor to quit any app that's using more than its fair share of resources. In the Activity Monitor window, you can see real-time stats on the amount of CPU and memory resources each app is using. Open the Activity Monitor (by searching for it or finding it in the Utilities folder, which is inside your Applications folder) to see how much of an impact the apps you are currently running have on your system resources. If you are seeing the spinning beach ball with increasingly regularity, then it's time to take a look at what might be causing the slowdown. (You can also select multiple apps to force quit by using holding down the Command or Shift keys when making your selections.) Just highlight the app that's not responding and hit the Force Quit button. You can call up the Force Quit menu from the Apple icon in the upper-left corner or by hitting Command-Option-Escape. And when an app hangs, it freezes you out and won't let you do anything, including quit out of it. You might find that an app will occasionally trip up your Mac and hang. You can add items back to the Startup Items list by hitting the "+" button and selecting items from your Applications folder. If not, you can head back to the list and remove another app and keep going until you find the culprit. It'll get removed from the Login Items list and you can restart your Mac to see if your startup issue has been fixed. Highlight an app and then click the "-" sign below. Next, click the Login Items tab above the window to the right.
To do so, go to System Preferences > Users & Groups and click your name on the left under Current User. You can remove login items one at a time and start up your Mac after each removal to see if the problem is gone.
#VS CODE FOR MAC CAUSES FREEZING TRIAL#
With a bit of trial and error, you can identify which app is the problem child. If you find yourself staring at a blue screen when you start up your Mac, it might mean that one of your startup items - apps that start automatically when you start up your Mac - is incompatible with MacOS.
To leave Safe Mode and start up your Mac per usual, just restart your Mac without holding any keys. It may take a few minutes before you get to the login screen as MacOS runs its diagnostics on your hard disk. You can release the Shift key when the Apple logo disappears and the login screen appears. The Apple logo will appear and then the login screen. To start up in safe mode, start your Mac and then press and hold the Shift key.
#VS CODE FOR MAC CAUSES FREEZING DRIVERS#
In Safe Mode, MacOS will boot with the bare minimum of software and drivers required and will run a check of your startup disk and repair any directory issues that might be the cause of your startup ills. If your Mac fails to boot properly and you find yourself staring at a blank screen or gray startup screen instead of your desktop, then it's time to try booting in Safe Mode.
0 kommentar(er)
