Does this only happen when you run chromium within a debugger?  I think that the SIGPIPE you're getting in that 
backtrace should normally be safely ignored.

No. even without GDB (i started a brand new profile) it starts showing a Kill 
Tab popup (as i reported on an earlier bug), until the pages snaps, and the 
browser freezes

Please explain in more detail about what you mean when you say the browser "hangs".  
And please attach the debugger to the browser after it "hangs" and do "thread apply 
all bt" in gdb.  Does the browser still paint properly?  Like, if you move windows in 
front of it and then away, will show the contents of the other window, or will 
chromium repaint its own contents properly?  Will you be able to open new tabs using 
"ctrl-t"?  What if you press the "+" button on the tabstrip?

Will if i'm running without dbg, i get a popup (i can attach a screenshot if needed) 
asking me to kill that tab, and when i do so, all tabs of that domain die with the 
famouse oh snap.
freshing that page will lead to the browser stop working.

if i run it with GDB, then i get the trace like the one attached in the 1st post.
i'm not sure how else i can provide input for this situation... feel free to ping me 
on IRC, i'll try to idle in #chromium

It sounds like your renderer is hanging.  That's one bug.  Then when the renderer 
hangs, you kill the tab.  Refreshing it hangs the browser.  That's a separate bug.  
Sounds like 2 bugs to me.

For the first one, we should try to figure out what is hanging.  When it happens, can 
you bring up the task manager (shift-esc) to figure out the pid of the renderer.  Then 
use gdb to attach to the pid and get a stacktrace?

For the second one, you still haven't described exactly what you mean by the browser 
"stops working".  Please answer my questions in #3.  I'm copy/pasting them here:

"Does the browser still paint properly?  Like, if you move windows in 
front of it and then away, will show the contents of the other window, or will 
chromium repaint its own contents properly?  Will you be able to open new tabs using 
"ctrl-t"?  What if you press the "+" button on the tabstrip?"

Also, you didn't paste the about:version for your Chrome version.  I can't tell which 
operating system you're running on.

i havent had it happen in the last 24h or so.
i did mention in the OP the version.
the current installed version is: 
6.0.409.0 (47612) from Launchpad dailly chromium PPA by fta
Using it on Debian Unsteable 64bits

i'm still running chromium in GDB, so if/when it happens again, i should be able to 
capture it.

sooo it just happend on a fresh profile.

$ chromiumdatadir="$(mktemp -d)";chromiumdiskcache="$(mktemp -d)";chromium-browser -g 
--user-data-dir=$chromiumdatadir --disk-cache-dir=$chromiumdiskcache


#1 shift-esc doesnt work (but it may be locked in GDB breakpoint)
#2 its just grayed as the screenshot attached (left window)
#3 6.0.409.0 (47612) 

	Screenshot.png 109 KB View Download

ch 30.0 KB View Download

This is just happening because you're getting SIGPIPEs, which chromium will ignore, 
but gdb will catch.  You need to make sure you ignore SIGPIPE in gdb.  Running 
something like `handle SIGPIPE nostop noprint pass` in gdb will do it.  I put that in 
my ~/.gdbinit file.  This isn't a bug.  Let me know if there is any other issue, 
otherwise I will close this bug as WontFix.

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.