MicroB just displays white
 

Today on my way back home I was trying to check some news, and again this annoying thing hit me.
I open a link in a new window, the new window opens and becomes active. I then go to dashboard, and return to the news site to let the opened page load on the background. When I activate the browser window containing the news site, it briefly (split-second) flashes the site as it was before opening the new window, then goes white:
http://img64.imageshack.us/img64/174...1031818543.png

After being white for a moment (usually 1-5 seconds, but almost indefinitely at worst), the page is redrawn. Sometimes it just doesn't appear at all, and remains white. If I try to go to the browser window I recently opened, it sometimes may flash the loaded page, and then always goes white.

Finally I may end up with a situation like this:
http://img4.imageshack.us/img4/1590/...1031818542.png

None of the windows show any page contents, although some had loaded the page already. When I try to open the windows, they just go white and stay that way. CPU usage was 100%, and according to htop, Xorg was using 55-75% most of the time while browserui was using something rather minimal.

I had this MicroB issue before reflashing, too, and prior to installing any plugins.

Why does the browser even have to redraw the once-already-loaded page contents when I return to it from the dashboard? When this hits, I can't do really anything. I tried to take screenshots of htop too, but none of the commands apparently got through due to system load.

Re: MicroB just displays white
 

I see you have a similar problem that I get, where opening a new window in MicroB sometimes the address bar to be the full width of the screen. So I have to use Ctrl+Bckspc or ShortcutD (focus) to get to the task manager, or hit the power button and End Current Task.

Re: MicroB just displays white
 

Ah, I've subconciously automated that task so that I always close browser windows through the task switcher. I always found it faster than first disabling full-screen mode and then tapping the X.

I think I saw a thread on the issue you described.