---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 18, 2017 at 4:08 AM, Michel Dänzer wrote:
> On 18/04/17 11:55 AM, Luke Kenneth Casson Leighton wrote:
>> On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer wrote:
>>
On 18/04/17 11:55 AM, Luke Kenneth Casson Leighton wrote:
> On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer wrote:
>
>>> far from being 100% reproducible when resizing glxgears under fvwm2
>>> with DRI2, glxgears freezing is now 100% *un*reproducible.
>>
>> Please attach the
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer wrote:
>> far from being 100% reproducible when resizing glxgears under fvwm2
>> with DRI2, glxgears freezing is now 100% *un*reproducible.
>
> Please
On 17/04/17 11:38 PM, Luke Kenneth Casson Leighton wrote:
> ok so i ended up with an unancipated reboot, which meant i had an
> opportunity to test DRI3 and since setting Option DRI "3" in
> xorg.conf i have *not* encountered a *single* lock-up, not with
> chromium, nor glxgears, nor openscad.
ok so i ended up with an unancipated reboot, which meant i had an
opportunity to test DRI3 and since setting Option DRI "3" in
xorg.conf i have *not* encountered a *single* lock-up, not with
chromium, nor glxgears, nor openscad.
far from being 100% reproducible when resizing glxgears under
ok i've raised this directly upstream with the mesa-dev team on
freedesktop.org and also done a little investigation, and found that
the processes are hanging waiting in a poll in libxcb. the mesa-dev
team asked everyone who is affected *AND NOT* affected to report which
version of DRI is being
ha, that's very interesting: since starting the chat with my friend on
facebook (a developer in china) for about 90 minutes i have had
*three* lockups (each time recoverable with ctrl-alt-f1, ctrl-alt-f7).
one in particular the cursor moved off-screen for a fraction of a
second and back again
haaa! finally... after waiting for well over a week, at last! the
bug *did* in fact reoccur.
just to make sure we're on the right page this is from the chrome://version
Chromium 56.0.2924.76 (Developer Build) built on Debian 9.0, running
on Debian 7.4 (64-bit)
Revision
On Thu, Feb 23, 2017 at 9:41 PM, Ximin Luo wrote:
> Luke Kenneth Casson Leighton:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
>>
>> now ain't that fascinating. optirun combined with fvwm2 is a
>> sure-fire extremely fast and 100% *guaranteed* way to repro
Luke Kenneth Casson Leighton:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
>
> now ain't that fascinating. optirun combined with fvwm2 is a
> sure-fire extremely fast and 100% *guaranteed* way to repro this
> "freezing but you can ctrl-alt-f1 then ctrl-alt-f7 and it miraculously
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
now ain't that fascinating. optirun combined with fvwm2 is a
sure-fire extremely fast and 100% *guaranteed* way to repro this
"freezing but you can ctrl-alt-f1 then ctrl-alt-f7 and it miraculously
all works whoopidoo" problem.
primus (and
btw fyi https://bugs.chromium.org/p/chromium/issues/detail?id=675411
i noted a vast and i mean constant monotonous barely-tolerable number
of gpu freezing errors when operating inside of china. i therefore
suspect that this is a race condition between networking code and the
gpu code.
l.
ah ha! when i did the latest "kill" i got this:
[11121:11121:0207/112924:ERROR:gpu_process_transport_factory.cc(844)]
Lost UI shared context.
Ximin Luo:
> Control: affects -1 + vlc mpv gnome-mpv baka-mplayer
>
> (I am using a personal package of baka-mplayer that I built for #813591 but
> it's doesn't follow Debian policy in some areas so I can't upload it yet.)
>
> Ximin Luo:
>> [..]
>>
>> A shorter workaround:
>>
>> $ pkill -f
On Sat, 21 Jan 2017 16:56:40 -0500 Michael Gilbert wrote:
> Is this #801128?
I don't think so since I couldn't reproduce the bug the way the reporter
described it (via octave-cli).
Best,
--
Douglas A. Augusto
signature.asc
Description: PGP signature
Douglas A. Augusto wrote:
> This trick works for me too. By the way, I just found out that the reported
> bug also affects octave-gui (4.0.3-2+b2), which randomly freezes just like
> chromium. And the exact same trick you described also works with
> octave.
Is this #801128?
Best wishes,
Mike
control: tag -1 moreinfo
Since this also effects upstream google-chrome, and other applications
like octave-gui, it may be more likely a mesa, X11, or gpu driver bug.
For those willing to dig in, try rolling some of the underlying
packages back a few months.
Best wishes,
Mike
Package: chromium
Version: 55.0.2883.75-2
Severity: important
Dear Maintainers,
Chromium randomly freezes for me frequently. This means the chromium
window is completely unresponsive and the process can only be
terminated using the SIGTERM signal or the xkill command. I can't see
any patterns
18 matches
Mail list logo