The following causes the IDE to become unusable on a MacBook Pro with Retina Display:
You just have to type that anywhere in the sketch in uncommented code and the IDE will become extremely difficult to use after that. In fact, you just have to type noDisplay by itself, without an object or the ".();". The exact symptoms are the following: 1. The line with noDisplay in it will disappear starting from the noDisplay part and going rightwards 2. Several lines after that may get screwed up visually. They may not screw up initially but they will if you start freaking out and trying to move the cursor around and do things. 3. The cursor will seem to move all around the window. (IIRC this is caused by attempting to move the cursor around to find your code - I admit I haven't tried it in a while because it's frustrating to fix the problem if you get your real cursor too far away from the offending line) 4. Scrolling causes more lines to disappear.
It doesn't mess up the file - as in, you can still go by memory of where your cursor was and move it around and all disappeared lines will still be there, or you can just hit undo. If you comment out the noDisplay line, your text will immediately reappear (including the commented noDisplay line) and go back to normal. I've been googling about this for a few months and have never turned anything up, so I guess I'm the only one with this problem. I've downloaded different versions of the IDE and they all do the same thing. It doesn't happen on my other systems - just my MacBook Pro with Retina display, running OS 10.8.
I will soon be finding out if it can compile with this offending line in it because I really need it for a sketch. Up until now, I've been able to avoid using it, but my current project will need it to keep power usage down. I do have Windows machines I can use instead but the MBP is by far my most favourite machine I've ever owned. I use it for everything as much as possible.
Thanks for reading!
P.S. The opposite command, display(), works fine. In fact I haven't come across anything else that causes this issue.
Oh and if this is a known problem with a known solution and I was just too stupid to find it, please point me in the right direction.
Java version: WAS 1.6, updated to 1.7 (sacrificed Chrome for that - hello FireFox). Terminal still reports 1.6, though, and I don't know why. The Java control panel is now installed and says it's running 1.7. Maybe both versions are still installed. I don't know if I can change that. Anyway, problem persists.
Edited: I was a bit wrong about a couple of the details. Added Java info.