I am using the M1 Macbook Pro. I have noticed this problem while using jupyter and multiprocessing library together. Not sure the problem is specific to this combination, but that combination is where I experienced it multiple times. Every time I interrupt a kernel while multiprocessing.Pool.map is running my computer freezes, then crashes, and restarts.
Does anyone know why this happens or if there is a fix?
Related
I find when I run create react app on my laptop then begin to code in VSCODE my laptop heats up a lot more than usual to the point its burning to the touch.
I have a macbook pro 2018 macos mojave fully upto date i5 8gb ram.
Is the reason for this low ram of 8gb?
Any information would be amazing.
Thanks
Nav
Not sure what to try?
npx create-react-app
Not expecting laptop to get unusually hot. Only happens when running create react app. also sometimes happens when running Atom IDE but does anyone even use that anymore?
No, the amount of ram you have should be more than sufficient to to VSCode and a create-react-app. Ram also has little impact on heat so I don't think that is causing the issue.
What you could try is to open the activity monitor to check if any processes are using more CPU than they should. Also check under the Energy-tab, that could give you a good guidance to what is causing your heating problem. As an example, I've had problems before where some of my VSCode plugins have had a bug that causes them to run at 100% CPU constantly.
A note:
I'm working on reverse engineering a certain OS X driver dependent on physical hardware, so a VM environment just won't do.
In my environment I have 2x 2015 Macbook Pro's running OS X 10.11.6 (15G18013) and have installed the latest KDK on both. To perform the remote debugging I setup network debugging over Ethernet using a Thunderbolt NIC on the second machine.
I have lldb working for the most part. I can set breakpoints, resume the kernel and breakpoint just fine, but the problem is after some time of doing ni (next instruction) I get the error error: invalid thread, and I can't send anymore commands to the other machine. When in this state the machine is still frozen (since I was stepping over instructions) and I can't seem to reattach to the other machine either, even after doing an NMI.
The latest KDK for 10.11.6 is 15G17023. You can downgrade or wait for apple to release 15G18013.
I have the same problem if I want to test the latest updates from apple with a kext.
I'm running macOS Sierra, but same experienced on High Sierra.
When I open the Simulator in Xcode 9.1, it doesn't load anything (sometimes a red screen), however crashes the whole system. I can move the mouse, but everything is unclickable.
Really rarely it receives clicks and I can open the Activity Monitor to shut it down. Restart doesn't help, because Simulator is reopened then, and crashes the whole system again.
Is there anyone out there experiencing the same issue? Any solutions, suggestions?
Could this relate to the fact that I have a Hackintosh?
We can't provide support for pirate copies of macOS running on non-Apple hardware. I would encourage you to purchase authorized Apple hardware which comes with a legal copy of macOS.
Red is the canary texture indicating the GPU didn't write anything to the surface. It is probably a rendering failure due to graphics driver bugs. You can check the logs in cases where it doesn't fully restart and you may find GPU restarts are taking place. If the GPU restart fails then the system will panic and reboot.
Edit: As I previously indicated, you're running untested hardware on a hacked copy of macOS using unknown drivers. If you're using built-in drivers it may be a mis-match between the hardware they expect and the GPU you have. If you're using vendor-provided drivers it may be a simple bug. And when running any non-standard kernels or kernel extensions there could be a vast array of possible causes (bad kernel extension corrupting some data structure, etc)
I've written a signal processing program in Haskell. I've developed the program on my MacBook Pro, using OS X. I also own a desktop which runs Windows. Since my desktop has a more powerful CPU and GPU, I wanted to test my program on it to see how much quicker it would process certain signals, but I did not expect the results.
On my MacBook Pro, the program finishes in an average of 0.013s. On my Windows desktop, the program finishes in an average of 0.090s. This was extremely surprising to me and I started doubting the power of my desktop.
I also have Windows installed on my MacBook Pro in bootcamp, so I decided to test the program that way as well. In Windows (bootcamp), the program finishes in an average of 0.109s.
How is this possible. Is it normal for there to be a performance difference between Windows and OS X for Haskell. Am I missing something?
Currently i'm developing a Cocos2d application for Mac OS X using xCode 4.2.1.So my problem is,sometimes while running the program the system get's stuck and show me a message like this- You need to restart your computer.Hold down the power button until it turns off.Then press the power button again. After receiving this message i can't proceed further without restarting the computer. What might be the problem behind this issue. Can anyone help me out.
What You get is called a kernel panic.
Resolution
Restart your Mac with a Safe Boot and see if the kernel panic happens
again
In most cases, kernel panics are not caused by an issue with your Mac.
They are most likely caused by an issue external to your Mac. If the
kernel panic doesn't happen again within a few weeks, you don't need
to troubleshoot further.
Depending on the model of Mac you have, restart one of these ways:
• Press and hold the Power button for several seconds to turn off your Mac. Then, press the Power button to startup your Mac.
• If you have a Restart button, press it.
As soon as your Mac starts up, hold down the Shift key to start up with a Safe Boot into Safe Mode. Note: If you are using a third-party
external keyboard and cannot start with a Safe Boot, try using an
Apple keyboard instead.
If your Mac has a kernel panic starting up, or while in Safe Mode, jump to the "Troubleshooting a recurring kernel panic" section of this
article.
If your Mac starts up without a kernel panic after a Safe Boot, restart your Mac by choosing Apple Menu > Restart…, then let it start
up normally. Run Software Update and install all available updates
until Software Update reports "Your software is up to date". Mac OS X
updates improve the tolerance for external issues such as malformed
network packets. For most kernel panics, this is all you have to do.
Note: It is possible, although very unlikely, that something on your network is sending your Mac malformed network packets which could cause recurring kernel panics. If the hardware and software on your Mac checks out as OK, check the devices on your network. Make sure your router's firmware is up-to-date, and that the router is not malfunctioning. Refer to your router's manufacturer for service and support.
And You also can try to find the problem in kernel.log. Go to the console app in the utilities folder and then type this:
tail -f /var/log/kernel.log
It will print kernel.log file to Your console.
More information:
Kernel Logs from the Command Line in Mac OS X.
How to log a kernel panic.
Kernel Panic.