[ UPDATE 1: After a fourth reboot, the browser is now loading pages, although they are taking a little longer to load than would be ideal. Hopefully the overclock mod will improve that. Instant search in Google is working and updating quickly enough to be useful, though.
UPDATE 2: After about ten minutes of browsing through several pages and tabs and trying to download AppBrain, the browser force-closed. When I restarted the browser and tried to download AppBrain again, the process seemed to succeed, but, nothing was actually downloaded. This is not what I would call "stable", or "no issues", as others have suggested. At least it hasn't force-closed again after about an hour, with half a dozen tabs open to a few dozen pages. ]
Is anyone having trouble with the Honeycomb browser stalling during page loads? Even with just the browser running and one tab open, the blue progress "blip" running across the top of the browser window stops moving right about 35% of the way across, and only a few page elements are displayed. Sometimes, if I hit the stop button, the page contents will appear, and if I use the back and forward buttons, whatever of each page has already loaded will usually reload relatively quickly (but, not as fast as most tablet browsers do). And, yes, I did try rebooting several times.
I'm running the HC v4 from a 4 GB microSD card, there's over 1.1 GB of space left on the card's HC partition, and there's 570 MB of free space in internal storage, so, that's plenty to be able to run the browser with just one tab open. Just in case, I'm going to enlarge the user partition to use the rest of the SD card's space. The HC download is sized for 1.25 GB, which seems a bit strange - why not size it for a 2 GB card, or 4 GB, since that would provide a reasonable amount of space, and 4 GB cards are now the most cost-effective size?
Everything else seems to work pretty well - I did have a temporary issue when trying to enter the password for my wireless access point where it would skip past the option to allow the password to be viewed as it's being typed, and wouldn't connect. After trying a second access point, that worked, and then when I went back to the first access point, I was able to log in and connect.
Thanks for the effort to port to the NC, in any case!