I can't say I've shared your experience with Subclipse or Subversive. Switching sometimes takes a while (most of our working copies are in the 400MB range), but I've never had it crash out. In any case, you should be able to issue a Cleanup command, and then reswitch and pick up where you left off.

TortoiseSVN is one of a handful of apps that keep me using Windows (for now), although soon it will be relegated to a VirtualBox.

You haven't had any problems with what?

svn has this feature where it shows "all changed paths" of a checkin. You can turn off the view that displays this in the history view. When off, subclipse does not retrieve this information. The bug in subversive is that it does retrieve this information regardless. In our case, the entire source was checked into the repository in rev 9. The change set therefore includes all paths in our repository, about 30MB worth of data if pasted into a text file. So subversive would go and download 30MB worth of data every time I wanted to look at the history of a file, and it affected all files since they are all part of the first change set. That made subversive unusable for me.

The one feature I am missing from both is a "move change to branch" command which quickly and easily can move a change in trunk to a path. The equivalent of svn merge, but with automatic tag/branch detection and automatically filling in the correct parameters. I often work in /trunk, then we decide a fix/feature needs to go in the current release branch… automating this would be awesome.