12:28 p.m.
Dear All,
I have
google-chrome-stable-54.0.2840.100-1.x86_64
running on F25, but it deadlocks so often. Any solutions?
Thanks in advance,
Paul
12:39 p.m.
On Wed, Nov 23, 2016 at 06:28:26PM +0000, Paul Smith wrote:
Dear All,
I have
google-chrome-stable-54.0.2840.100-1.x86_64
running on F25, but it deadlocks so often. Any solutions?
Thanks in advance,
Can you describe the deadlock situation? Does it happen in any
particular circumstance, or seemingly at random?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
2:12 p.m.
On Wed, Nov 23, 2016 at 6:39 PM, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
> Dear All,
> I have
> google-chrome-stable-54.0.2840.100-1.x86_64
> running on F25, but it deadlocks so often. Any solutions?
> Thanks in advance,
Can you describe the deadlock situation? Does it happen in any
particular circumstance, or seemingly at random?
Thanks, Matthew. The reported problem occurs when one tries to open
Google Drive, for instance.
Paul
5:28 p.m.
On Wed, 2016-11-23 at 20:12 +0000, Paul Smith wrote:
On Wed, Nov 23, 2016 at 6:39 PM, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
> > Dear All,
> > I have
> > google-chrome-stable-54.0.2840.100-1.x86_64
> > running on F25, but it deadlocks so often. Any solutions?
> > Thanks in advance,
>
> Can you describe the deadlock situation? Does it happen in any
> particular circumstance, or seemingly at random?
Thanks, Matthew. The reported problem occurs when one tries to open
Google Drive, for instance.
Works for me. By deadlocked do you mean frozen (an actual deadlock
would be very hard to diagnose)? Have you tried disabling extensions?
poc
5:22 a.m.
On Wed, Nov 23, 2016 at 11:28 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> > > Dear All,
> > > I have
> > > google-chrome-stable-54.0.2840.100-1.x86_64
> > > running on F25, but it deadlocks so often. Any solutions?
> > > Thanks in advance,
> >
> > Can you describe the deadlock situation? Does it happen in any
> > particular circumstance, or seemingly at random?
>
> Thanks, Matthew. The reported problem occurs when one tries to open
> Google Drive, for instance.
Works for me. By deadlocked do you mean frozen (an actual deadlock
would be very hard to diagnose)? Have you tried disabling extensions?
Thanks, Patrick, for your reply.
And yes, I mean frozen instead of deadlocked. Following your advice, I
have disabled all extensions, but the problem persists. Any further
ideas?
Paul
5:43 a.m.
On Thu, Nov 24, 2016 at 7:22 PM, Paul Smith <phhs80(a)gmail.com> wrote:
On Wed, Nov 23, 2016 at 11:28 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
>> > > Dear All,
>> > > I have
>> > > google-chrome-stable-54.0.2840.100-1.x86_64
>> > > running on F25, but it deadlocks so often. Any solutions?
>> > > Thanks in advance,
>> >
>> > Can you describe the deadlock situation? Does it happen in any
>> > particular circumstance, or seemingly at random?
>>
>> Thanks, Matthew. The reported problem occurs when one tries to open
>> Google Drive, for instance.
>
> Works for me. By deadlocked do you mean frozen (an actual deadlock
> would be very hard to diagnose)? Have you tried disabling extensions?
Thanks, Patrick, for your reply.
And yes, I mean frozen instead of deadlocked. Following your advice, I
have disabled all extensions, but the problem persists. Any further
ideas?
works fine for me here also..... even with extensions adblock and
privacy badger enabled ....
> Paul
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
5:47 a.m.
On Thu, 2016-11-24 at 11:22 +0000, Paul Smith wrote:
On Wed, Nov 23, 2016 at 11:28 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> > > > Dear All,
> > > > I have
> > > > google-chrome-stable-54.0.2840.100-1.x86_64
> > > > running on F25, but it deadlocks so often. Any solutions?
> > > > Thanks in advance,
> > >
> > > Can you describe the deadlock situation? Does it happen in any
> > > particular circumstance, or seemingly at random?
> >
> > Thanks, Matthew. The reported problem occurs when one tries to open
> > Google Drive, for instance.
>
> Works for me. By deadlocked do you mean frozen (an actual deadlock
> would be very hard to diagnose)? Have you tried disabling extensions?
Thanks, Patrick, for your reply.
And yes, I mean frozen instead of deadlocked. Following your advice, I
have disabled all extensions, but the problem persists. Any further
ideas?
Not really I'm afraid. You could try running strace on the process when
it freezes, but that's unlikely to be very illuminating (Chrome runs a
lot of processes so even figuring out which one is to blame is likely
to be non-trivial). You haven't said if this happens randomly or only
on specific pages. If it's the latter, tell us what it is and others
can check if it works for them.
Another option would be to try it from a freshly-created user account.
Possibly something in your cache is messing it up. (You aren't by any
chance running it as root are you? Very bad idea as I'm sure you know).
poc
12:27 p.m.
On Thu, Nov 24, 2016 at 11:47 AM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> > > > > Dear All,
> > > > > I have
> > > > > google-chrome-stable-54.0.2840.100-1.x86_64
> > > > > running on F25, but it deadlocks so often. Any solutions?
> > > > > Thanks in advance,
> > > >
> > > > Can you describe the deadlock situation? Does it happen in any
> > > > particular circumstance, or seemingly at random?
> > >
> > > Thanks, Matthew. The reported problem occurs when one tries to open
> > > Google Drive, for instance.
> >
> > Works for me. By deadlocked do you mean frozen (an actual deadlock
> > would be very hard to diagnose)? Have you tried disabling extensions?
>
> Thanks, Patrick, for your reply.
>
> And yes, I mean frozen instead of deadlocked. Following your advice, I
> have disabled all extensions, but the problem persists. Any further
> ideas?
Not really I'm afraid. You could try running strace on the process when
it freezes, but that's unlikely to be very illuminating (Chrome runs a
lot of processes so even figuring out which one is to blame is likely
to be non-trivial). You haven't said if this happens randomly or only
on specific pages. If it's the latter, tell us what it is and others
can check if it works for them.
Another option would be to try it from a freshly-created user account.
Possibly something in your cache is messing it up. (You aren't by any
chance running it as root are you? Very bad idea as I'm sure you know).
Thanks, Patrick, for your reply. I have been waiting for figuring out
a systematic way conducing to the frozen state, but I am still with no
clue...
I have also erased Chrome's cache and history, but to no effect.
Moreover, I have re-installed Chrome. Maybe, I should mention that F25
was installed on my machine by upgrading from F24.
Paul
3:47 p.m.
On Thu, 2016-11-24 at 18:27 +0000, Paul Smith wrote:
I have also erased Chrome's cache and history, but to no effect.
Moreover, I have re-installed Chrome. Maybe, I should mention that F25
was installed on my machine by upgrading from F24.
As was mine. Reinstalling a package in Linux is usually a waste of
time, unlike Windows. Any configuration data will still be there from
earlier (in your home directory, which package removal does not touch).
Trying it under a different user account is a way to avoid these
effects without having to remove anything.
poc
3:49 p.m.
On 11/25/16 05:47, Patrick O'Callaghan wrote:
On Thu, 2016-11-24 at 18:27 +0000, Paul Smith wrote:
> I have also erased Chrome's cache and history, but to no effect.
> Moreover, I have re-installed Chrome. Maybe, I should mention that F25
> was installed on my machine by upgrading from F24.
As was mine. Reinstalling a package in Linux is usually a waste of
time, unlike Windows. Any configuration data will still be there from
earlier (in your home directory, which package removal does not touch).
Trying it under a different user account is a way to avoid these
effects without having to remove anything.
Same thing here. System upgraded from F24->F25. Running KDE, no wayland, and Chrome
continues to work as it did prior to the upgrade.
--
You're Welcome Zachary Quinto
6:35 p.m.
On Thu, Nov 24, 2016 at 9:49 PM, Ed Greshko <ed.greshko(a)greshko.com> wrote:
>> I have also erased Chrome's cache and history, but to no
effect.
>> Moreover, I have re-installed Chrome. Maybe, I should mention that F25
>> was installed on my machine by upgrading from F24.
> As was mine. Reinstalling a package in Linux is usually a waste of
> time, unlike Windows. Any configuration data will still be there from
> earlier (in your home directory, which package removal does not touch).
> Trying it under a different user account is a way to avoid these
> effects without having to remove anything.
Same thing here. System upgraded from F24->F25. Running KDE, no wayland, and Chrome
continues to work as it did prior to the upgrade.
It appears that by disabling gpu when calling Chrome, the problem is fixed:
google-chrome-stable --disable-gpu
I will confirm that later.
Paul
10:25 p.m.
On 11/25/16 08:35, Paul Smith wrote:
It appears that by disabling gpu when calling Chrome, the problem is
fixed:
google-chrome-stable --disable-gpu
I will confirm that later.
Well, if that does fix your problem then the obvious follow-up question would be.....
What is your Video Hardware and drivers.
--
You're Welcome Zachary Quinto
4:38 a.m.
On Fri, Nov 25, 2016 at 4:25 AM, Ed Greshko <ed.greshko(a)greshko.com> wrote:
> It appears that by disabling gpu when calling Chrome, the problem
is fixed:
>
> google-chrome-stable --disable-gpu
>
> I will confirm that later.
Well, if that does fix your problem then the obvious follow-up question would be.....
What is your Video Hardware and drivers.
Yes, Ed, I can now confirm that disabling gpu when calling Chrome
fizes the problem.
My video hardware and drivers are below.
Thanks,
Paul
------------------------------
$ lspci -k | grep -A 2 VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] RV710 [Radeon HD 4350/4550]
Subsystem: Dell Device 904e
Kernel driver in use: radeon
$
$ grep driver /var/log/Xorg.0.log
[ 64.635] X.Org XInput driver : 24.1
[ 65.083] (==) Matched ati as autoconfigured driver 0
[ 65.083] (==) Matched ati as autoconfigured driver 1
[ 65.083] (==) Matched modesetting as autoconfigured driver 2
[ 65.083] (==) Matched fbdev as autoconfigured driver 3
[ 65.083] (==) Matched vesa as autoconfigured driver 4
[ 65.083] (==) Assigned the driver to the xf86ConfigLayout
[ 65.206] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[ 65.247] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[ 65.377] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 65.425] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 65.449] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 65.476] (II) FBDEV: driver for framebuffer: fbdev
[ 65.476] (II) VESA: driver for VESA chipsets: vesa
[ 65.730] (II) RADEON(0): [DRI2] DRI driver: r600
[ 65.730] (II) RADEON(0): [DRI2] VDPAU driver: r600
[ 71.825] ABI class: X.Org XInput driver, version 24.1
[ 71.825] (II) Using input driver 'evdev' for 'Power Button'
[ 73.220] (II) Using input driver 'evdev' for 'Power Button'
[ 73.221] (II) No input driver specified, ignoring this device.
[ 73.222] (II) Using input driver 'evdev' for 'USB Optical Mouse'
[ 73.224] (II) No input driver specified, ignoring this device.
[ 73.225] (II) Using input driver 'evdev' for 'Dell Dell USB Entry
Keyboard'
[ 73.226] (II) No input driver specified, ignoring this device.
[ 73.226] (II) No input driver specified, ignoring this device.
[ 73.227] (II) No input driver specified, ignoring this device.
[ 73.227] (II) No input driver specified, ignoring this device.
[ 73.228] (II) No input driver specified, ignoring this device.
[ 73.228] (II) No input driver specified, ignoring this device.
[ 73.229] (II) No input driver specified, ignoring this device.
[ 73.229] (II) No input driver specified, ignoring this device.
$
8:06 a.m.
On Fri, Nov 25, 2016 at 10:47 PM, Ed Greshko <ed.greshko(a)greshko.com> wrote:
> Yes, Ed, I can now confirm that disabling gpu when calling
Chrome
> fizes the problem.
>
> My video hardware and drivers are below.
OK.... I have no similar HW available to me to test. :-(
Thanks anyway, Ed. Since with gpu disabling Chromes works fine, there
is no major problem!
Have a nice weekend,
Paul
7:22 a.m.
On Sun, Mar 19, 2017 at 11:53 AM, Leopold Schabel
<leoluk(a)fedoraproject.org> wrote:
I opened a Chromium bug: https://crbug.com/702960
Thanks, Leopold.
Paul
2588
days inactive
2704
days old
16 comments
6 participants
participants (6)
-
Ed Greshko -
Leopold Schabel -
Matthew Miller -
Outback Dingo -
Patrick O'Callaghan -
Paul Smith