4 ms·
Yes, I've never had OS X crash as often as Mavericks. And some of the crashes are completely repeatable. For example, open a lot of windows (20 terminal window
by song 12y ago
Yes, I've never had OS X crash as often as Mavericks. And some of the crashes are completely repeatable.
For example, open a lot of windows (20 terminal windows, 5-6 projects in Sublime, a bunch of browser windows used to test apps), turn on mission control and it just crashes every single time. I haven't done more test to figure the exact number of windows until it crashes but I know that it does for my workflow.
Admittedly, I tend to have more windows opened than most people, but then again that's what I have 16GB for.
I've also noticed that while expose was always smooth, mission control just doesn't work for me. If it doesn't crash it's dog slow, especially if it switches from integrated GPU to dedicated GPU just when I open it.
- epmatsw 12y agoIf it's that reproducible, it would probably be good to file a bug report with Apple.
- mentat 12y agoThere are and have been real GPU HW bugs that this could be triggering. I just had my main logic board replaced twice due to these with a similar trigger.
- FraaJad 12y ago20 terminal windows? Is there any reason you are not using screen/tmux?
- girvo 12y agoEh, why bother when iTerm2 gives me the same splitting and tab features :)
- zachrose 12y agoI used to have the same question, but having a remote tmux session that persists forever has turned out to be awesome.
- nknighthb 12y agoA remote session doesn't help when you're trying to run commands on your local system.
- DonHopkins 12y agoI helps me, because I always fat-finger Command-W close tab instead of Alt-W copy region to selection in Emacs, and it closes my tab. I can get it back when I run Emacs under screen!
- Moto7451 12y agoiTerm2's Tmux integration (native tabs and panes backed by a tmux session) lets you have your cake and eat it too it's my standard dev flow for remote or local work. Just add -CC when firing up tmux within iTerm2.
- recursive 12y agoPresumably because that doesn't cause the crash. It's a crash reproduction, not a workflow recommendation.
- pfranz 12y agoHave you tested your RAM? I had a similar situation where I had upgraded my memory and everything worked fine until I went to play Quake3. Also running Linux was miserable while Windows seemed to work ok. I finally figured out it was a bad stick of RAM and it save a lot of frustration.