Say you were working in an unspecified but extremely buggy beta SDK. Say you suddenly started encountering "could not open a new pseudo tty" errors whenever you tried opening a new terminal windows. There's not much help out there on the net for this extremely hypothetical situation. (You might also run into Xcode memory panics of a similar nature.) So what do you do? Logging out and back in won't fix the problem but a good fresh reboot will. If you should find that you're dealing with Leopard instability after running the EHSDK (that is, the extremely hypothetical SDK), put your memory issues to rest.
© 2011, O'Reilly Media, Inc. (707) 827-7000 / (800) 998-9938 All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. |
|
Sooo, about this hypothetical problem. Are there any hypothetical solutions?
I've only been able to workaround this by rebooting. This happens (for me) after a few hours of compile-test-endtask on the iphone simulator.
This also happens to me using the iPhone Simulator. My workaround was to use X11 instead of the terminal, but now not even X11 loads a terminal...
:(
If you kill all the "as" and "ccobj1" processes in activity monitor then terminal should start working again, avoiding a logout or reboot.
Thanks mav, that helped.