On Sat, Jan 09, 2016 at 04:07:05PM -0800, Marc MERLIN wrote:
> On Fri, Jan 08, 2016 at 09:42:24AM -0800, Marc MERLIN wrote:
> > On Sun, Jan 03, 2016 at 08:04:27AM -0800, Marc MERLIN wrote:
> > > My hunch at this point is that google-chrome-beta is taxing the GPU and
> > > causing the driver to misb
On Mon, Jan 11, 2016 at 09:41:47AM +1100, Daniel Kasak wrote:
> I noticed hard lockups using chrome from a *long* way back. Various
> people have reported issues with Chrome running under Enlightenment,
> and the consensus ( IIRC ) was that Chrome was using its own libX11
> parts or something, and
I noticed hard lockups using chrome from a *long* way back. Various
people have reported issues with Chrome running under Enlightenment,
and the consensus ( IIRC ) was that Chrome was using its own libX11
parts or something, and playing havoc with Enlightenment ( messing
with focus policy, crashing
On Fri, Jan 08, 2016 at 09:42:24AM -0800, Marc MERLIN wrote:
> On Sun, Jan 03, 2016 at 08:04:27AM -0800, Marc MERLIN wrote:
> > My hunch at this point is that google-chrome-beta is taxing the GPU and
> > causing the driver to misbehave. I'm now back to
> > 2:2.99.917+git20151217-1~exp1 and 4.3.3 an
On Sun, Jan 03, 2016 at 08:04:27AM -0800, Marc MERLIN wrote:
> My hunch at this point is that google-chrome-beta is taxing the GPU and
> causing the driver to misbehave. I'm now back to
> 2:2.99.917+git20151217-1~exp1 and 4.3.3 and will run google-chrome-beta
> --disable-gpu, but this kills other s
On Sat, Dec 19, 2015 at 08:52:17AM -0800, Marc MERLIN wrote:
> > Thanks both. I filed a bug as requested:
> > https://bugs.freedesktop.org/show_bug.cgi?id=93438
> >
> > It just crashed again, same crash. Looks like I'm going to get a crash every
> > 2 days or so at this stage.
>
> Sigh, same cras
