That's where the "if you can get it set up properly" comes in. Fortunately, Tear has come a long way towards beta lately.

I restart browserd all the time. What kind of unwanted side effects should I be experiencing?

I mainly get missing UI elements. Could you post a howto for restarting browserd?

First, I exit all browser windows. Then I watch and wait for the CPU to settle down (forget the name of the status bar plugin). And lastly, in an xterm I type:
Or for the less lazy:

hm, in order to get browserd to work with tsocks, it would involve a
and
to work... I wonder if that would be successful? Anyone want to try and report?

BTW: why do you restart browserd "all the time"?

There's a UI bug in there somewhere. Unfortunately, I can't faithfully reproduce it, but it seems to be related to either:

program switching and fast screen tapping

or maybe

page rendering and fast screen tapping

The result is a runaway CPU. It's probably a sight to see as I franticly try and get the program menu up to kill the b*stard(s). But because I'm a fanboy these things don't bother me much. In fact, I have another quirky browser workaround/speed-up:

First off, let me say, the X11 improvements from the last update are very welcome. That said, I have a strange suspicion that they might be involved in the above mentioned bug. Anyway, browser rendering speeds seem to increase when I minimize all browser windows that are in any stage of rendering; especially new ones from a tap-and-hold. It's kind of like a one-dimensional version of Whack-A-Mole, or in your case... I haven't done any formal analysis, but I would be shocked if it was just a busy-body placebo effect.

That paints a very interesting picture. daperl, madly whacking moles, as his CPU runs away into the sunset.

Sad, true and funny. I live near the top of a high-rise building, and there have been moments where the n800 could have flown into the sunset.