I was trying to install ruby on my Mac and i just opened terminal and it won't let me type anything in it, when i go to open it 2 windows pop up both with the same message on.
[forkpty: Resource temporarily unavailable]
[Could not create a new process and open a pseudo-tty.]
I don't really know what it means and i have never come across this problem before, i tried quitting terminal and restarting my Mac but it just does the same thing.
Any help is appreciated.
I have fixed this problem! I tried logging into guest user and then going back into my current user and it seems to have been fixed.
Related
Currentl i am unable to run docker on my mac anymore.
i keep getting this issue and its stuck i cant even click on anything i have to stop it using the activity monitor every time it comes
macOS : Big Sur 11.4
i have tried:
reinstall and uninstall
restart the device
i have no virtual machine so i did uninstall my parallels desktop
Please help and thanks in advance.
I found this issue documented here :
https://github.com/docker/for-mac/issues/5037
Based on the comments in the link you can try
Reset to factory defaults from the troubleshoot menu
First, I killed the hanging process using top | grep "Docker" then kill . Then, I went to my root folder in Finder, made sure permissions for my user were "Read & Write", and that those permissions were applied to items enclosed.
Hope it helps to dig deeper or solve the issue
My mac got a trash box always full soon. Even if I clean trash box, it cause over and over again.
Does anyone know what is dyld_shared_cache_arm64 files?
Please let me know how handle it.
I don't know the reason.
However I figured out.
Whenever I have my iPhone8 connect into Mac with USB Cabel.
Every one minutes, 1.62Gb back up file were made.
I stoped to connect iPhone8 and Mac to get charge.
Thanks.
Suddenly also happening to me, in my case, i was uninstalling and then installing again Xcode. After some time browsing i found this article that helped me, simply disconnect your phone, open Xcode, go to Window > Devices and Simulators
then
Connect your phone, after it appeared on Devices pane, unpair it, and then disconnect again, reconnect you phone, and do the pairing mechanism and it solved.
dyld_shared_cache means dynamic library shared cache.
Macos may share sth with IOS while connects to your IOS device.
This is the log in console.
2016-10-19 4:35:30.377 PM com.apple.CoreSimulator.CoreSimulatorService[761]: Error saving /Users/myusername/Library/Developer/CoreSimulator/Devices/14ABD200-69D3-441D-8FAA-731F5F00F678/data/tmp/com.apple.lsdidentifiers.plist : (null)
/Library/Developer/CoreSimulator/Devices/14ABD200-69D3-441D-8FAA-731F5F00F678/data/tmp/ is an empty folder.
Meanwhile, my xcode can not load xib or storyboard properly. "Internal error occurred, Editing functionality maybe limited"
I did clear /Users/myusername/Library/Developer/CoreSimulator/Devices/ folder, doesnt help, re-install xcode doesnt work.
environment: OS: EI 10.11.6, xcode: 8.0 simulator:Version 10.0 (SimulatorApp-700.5.3
The error message is benign and can be ignored. Sorry about the noise in syslog. The issue has since been resolved in the Xcode 8.1 betas.
If you deleted ~/Library/Developer/CoreSimulator/Devices while CoreSimulatorService was running, the service will be in an inconsistent state. You should SIGKILL it to cause it to relaunch in a new state.
Your 'Internal error occurred, Editing functionality maybe limited' error message is likely unrelated to either of those things. Most users see that because they're trying to use multiple copies of Xcode.app at the same time. It's perfectly fine to have multiple Xcodes installed, but you can only use one at a time. If that's not the issue you're seeing, you will need to provide more information about the error.
fixed it by turn off System Integrity Protection in El Capitan.
I totally have no idea when I updated mac os, and got this issue.
Until I noticed that I cant start mysql, which has similar issue 'Could not create unix socket lock file /tmp/mysql.sock.lock'
Then I thought something went wrong with my os settings.
steps:
Restart your Mac.
Before OS X starts up, hold down Command-R and keep it held down until you see an Apple icon and a progress bar. Release. This boots you into Recovery.
From the Utilities menu, select Terminal.
At the prompt type exactly the following and then press Return: csrutil disable
Terminal should display a message that SIP was disabled.
From the menu, select Restart
for more information https://apple.stackexchange.com/questions/193368/what-is-the-rootless-feature-in-el-capitan-really
I've got this weird problem from last night, where I cannot open Xcode anymore!
It is stuck with an empty tab loading view, and is just not responding... :-/
I have deleted Xcode4 and re-installed, it keep giving me that same problem... And also tried with Xcode 5, and still.... so I guess the problem is somewhere on my computer... What can I do?
Really need to fix this for work.
Found my solution on a similar linked problem :
Xcode freezes on startup while loading project
Due to the restore feature, all the windows you left open in a given application remain open when you relaunch it. To avoid this, discard the previously open windows by holding the option key while pressing CMD+Q. Try starting Xcode and quitting it with option held before it's had a chance to open your windows, then re-launch it and it shouldn't try to open the windows.
Fixed the problem for me.
I keep getting this error when launching my app on the iOS Simulator:
Couldn't register com.mycompany.MyApp with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.
I've read other reports of this error and it seems there is no obvious fix for it (restarting the iOS Simulator, restarting Xcode etc..)
At this point here's a list of things I've tried:
Restarting the Simulator
Restarting Xcode
Rebooting my machine
Deleting my app's Derived Data, and Cleaning
Deleting the iOS Simulator App Support directory
Reverting to a 2 weeks old version of the app (which was working 2 weeks ago)
Deleting the application in the Simulator (by clicking-holding on it and hitting the X button)
Upgrading Xcode form 4.1 to 4.2, and running the app both in iOS Simulator 4.3 and 5.0
Nothing worked, I still get the same bootstrap error.. Any (and at this point I really do mean ANY) suggestion would be appreciated.
Edit: Just wanted to add that the app runs fine on a device. I only get this error on the simulator...
As the GDB said:
This generally means that another instance of this process was already running or is hung in the debugger
So find out it and kill it. ;)
I restarted the mac, and it run successfully.
Tip: Well, this may be not work sometimes, so I strongly suggest that you press cmd+. to make sure that you do have stopped the simulator (or device). I find that in most cases the simulator (or device) will not stop exactly when it crashes. I rarely met this issue again with pressing the cmd+. every time it crashes or even just normal exit. Hope this will be helpful. :)
I just closed my xcode & restart my device(ipad2) and it works for me :)
You can try this :: Couldn't register with the bootstrap Server
Another solution, go to clear the memory of the iphone simulator
Simulator > recovery content and setting
then run the program again.
i just change the identifier and the app can work again.
I had to change my bundle identifier finally
No matter you reboot all devices and cleanup all , it gets stuck hard in the debugger..
don't know how to clear it..
As I experienced, device (or simulator) restart does solve the issue,
BUT it would be better not to couse it.
Also my experience is that:
You can find the place of crash by cousing it. In such time developers usually press "STOP the running scheme" this could cause zombie process stuck in device.
BUT
if you press "COUNTINUE program execution", debugger will terminate the process, it will not become a zombie.
I had this error too and I noticed that it works for me if you close the simulator and stop the program and then change your company name.
I don't know why but it works for me.
I opened Activity Monitor and searched for my app name, and found another instance of it listed. I used Activity Monitor to quit that instance, and the problem went away for me.