I do not know how to explain but since a couple of days I have a serious problem with chromium (www-client/chromium-34.0.1847.14-r1). Both on a Gentoo desktop installation and on a Funtoo desktop installation.

When opening various tabs, some tabs will freeze (I have not yet discovered if it are systematically tabs showing the same category of web pages). When going from a tab that works normally to a frozen tab, the frozen tab will just show the latest status of the previous (working) tab and it will take some time before I can use the mouse again (but the tab remains frozen)

I know the explanation is not perfect but it is the best I can give at present. Anybody else having a similar problem? Anybody having a suggestion (emerge -e system and emerge -e world does not solve the issue)?

kdvgent,
I'm sorry if my answer sounded rude. I just intended to warn you not to expect support when running a release candidate packages. Actually, these packages are very frequently used but at risk of their own users. If you want to discuss problems in release candidates you may want to joint the herd list of the corresponding package.
Best.

Same here. Tried to revert to previous version, but it does not resolve it.

I have an intel HD3000 (on sandy bridge) graphics card with SNA accel so I guessed that this can be a problem too.
Tried to disable HW accel in chromium and now it seems to work again - so my guess is the problem is with xf86-video-intel but did not try the older one yet.

Chalucha, thanks for the suggestion. Disabling HW acceleration indeed seems to help. As the latest update of xf86-intel-video dates back from 10 February, this is unlikely the cause of the problem.

Anyhow, I'll create a bug report.

Ferreirafm, no problem. I am not a systematic tester of new packages but run for almost ten years now unstable branches of Gentoo (or current branches of Funtoo) on my computers. Every now and then this gives a problem but nothing serious has ever happened - and if necessary I just rebuild my system. I create bug report whenever I can clearly describe the problems.

The default version of google-chrome-beta (AMD64, unstable) has changed. I installed and could - up to now - not get a tab to fail. Either something has changed between the previous version and this one that solved the problem or an update to an underlying package cured the problem.

I have updated the google-chrome bug report and will now recompile chromium and see what happens there.