FWIW, here is one trace:
(gdb) where
#0 0x1b6a980e in std::set_differencestd::_Rb_tree_const_iteratorint,
std::_Rb_tree_const_iteratorint, std::insert_iteratorstd::vectorint,
std::allocatorint() from /usr/local/chrome/chrome
#1 0x1b6a9708 in
frantisek holop, 24 Feb 2015 17:45:
however with or without, after exiting
there is always a core dump. i suspect
well, not always always, but quite often.
so far, i cannot find a pattern. starting
from shell (with/without backgrounding) and
starting from openbox menu.
is it even possible to
On Tue, Feb 24, 2015 at 04:45:37PM GMT, frantisek holop wrote:
with the Mesa rollback it is now possible
to run chromium again without --disable-gpu.
however with or without, after exiting
there is always a core dump. i suspect
this has been the case for some versions now.
anybody else
with the Mesa rollback it is now possible
to run chromium again without --disable-gpu.
however with or without, after exiting
there is always a core dump. i suspect
this has been the case for some versions now.
anybody else is seeing this?
-f
--
i'm weird, but i'm saving up to be eccentric.
On Tue, Feb 24, 2015 at 05:45:37PM +0100, frantisek holop wrote:
with the Mesa rollback it is now possible
to run chromium again without --disable-gpu.
however with or without, after exiting
there is always a core dump. i suspect
this has been the case for some versions now.
anybody
On Tue Feb 24 2015 at 11:45:50 AM frantisek holop min...@obiit.org wrote:
with the Mesa rollback it is now possible
to run chromium again without --disable-gpu.
however with or without, after exiting
there is always a core dump. i suspect
this has been the case for some versions now.
On 02/24/15 11:45, frantisek holop wrote:
with the Mesa rollback it is now possible
to run chromium again without --disable-gpu.
however with or without, after exiting
there is always a core dump. i suspect
this has been the case for some versions now.
anybody else is seeing this?
-f
