Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 310803 - www-client/chromium-4.0.356 - tabs belonging to domain crash after clicking a link/background, after some time
Summary: www-client/chromium-4.0.356 - tabs belonging to domain crash after clicking a...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Paweł Hajdan, Jr. (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-22 22:28 UTC by Piotrek Juzwiak
Modified: 2010-04-04 08:02 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.txt,3.27 KB, text/plain)
2010-03-23 22:48 UTC, Piotrek Juzwiak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Piotrek Juzwiak 2010-03-22 22:28:43 UTC
After some time (reading etc. on a site) clicking a link crashes ALL tabs belonging to domane. For example i read something on example.com/read1, then i click a link to example.com/read2 (havent checked if it crashes also when clickin a link outside the domain but i think it also crashes.

Reproducible: Always

Steps to Reproduce:
1.Install version 4.0.356
2.Stay some time on a website (don't know how long exactly)
3.Click a link pointing to another website

Actual Results:  
All the tabs belonging to the domain crash

Expected Results:  
It should open the new tab not crashing any other
Comment 1 Piotrek Juzwiak 2010-03-22 22:56:58 UTC
Looks like it crashes even if i click in the background of the website. There is some timeout when it starts to trigger. 
Comment 2 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-03-23 13:07:26 UTC
Please modify the summary to include what application you are talking about. Also post your emerge --info please.
Comment 3 Piotrek Juzwiak 2010-03-23 22:48:46 UTC
Created attachment 224971 [details]
emerge --info
Comment 4 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-03-24 08:09:12 UTC
Just to confirm - was it working fine for you in the previous versions of the browser?

Does it look like http://code.google.com/p/chromium/issues/detail?id=38414 ?
Comment 5 Piotrek Juzwiak 2010-03-24 12:24:25 UTC
The 4.0.342.5 version was working just fine. When i compiled the 4.0.356 version i noticed that bug, i switched back to 4.0.342.5 and didn't have that bug anymore. It's not that bug (code.google[...])
Comment 6 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-03-24 12:35:31 UTC
Are you able to obtain a backtrace? See http://code.google.com/p/chromium/wiki/LinuxDebugging for some tips.
Comment 7 Piotrek Juzwiak 2010-03-24 13:32:04 UTC
I installed gdb but it looks to me like this happens only on one site vigilantcitizen.com, i can't reproduce it on other websites. While it is dead easy to reproduce it on the above website clicking in the background/link does the trick of crashing all tabs. Change status of this bug to resolved?
Comment 8 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-03-24 13:44:24 UTC
If it's crashing it's clearly not resolved. I'll take a closer look later. Could you try to obtain a backtrace with gdb? Please note that you need to debug the renderer instead of the browser process. See http://code.google.com/p/chromium/wiki/LinuxDebugging for more details.
Comment 9 Piotrek Juzwiak 2010-03-24 17:26:31 UTC
I can't debug it, first there are no debugging symbols (understandable?) and second if i start chromium (or even directly the /usr/lib/chromium-browser/chrome ) with any proposed commands from google's website then i just can't browse anything, it becomes unresponsive no matter what website i try to go to and asks me to kill the unresponsive window.
Comment 10 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-04-04 07:51:16 UTC
I can't reproduce the crash with 5.0.366.2. I wonder if the CFLAGS you use could be a part of the problem.
Comment 11 Piotrek Juzwiak 2010-04-04 08:02:30 UTC
Yeah, it was an upstream fault of the 5.0.356 version, 5.0.360.5 resolved it.