On Tue, Sep 3, 2019 at 6:45 AM, Bastien Nocera
wrote:
Maybe release 3.32.x as a 3.34 instead if that's the problem?
We absolutely could, but have no way to know where the memory
corruption was actually introduced.
It could be an Epiphany regression (not unlikely). But it could also be
a
On Tue, 2019-09-03 at 06:42 -0500, mcatanz...@gnome.org wrote:
> On Sat, Aug 17, 2019 at 4:41 PM, mcatanz...@gnome.org wrote:
> > The bug report shows valgrind crashes on startup. I've tried to get
> > a
> > working asan build of Tech Preview, but haven't been successful.
>
> If anyone is
On Sat, Aug 17, 2019 at 4:41 PM, mcatanz...@gnome.org wrote:
The bug report shows valgrind crashes on startup. I've tried to get a
working asan build of Tech Preview, but haven't been successful.
If anyone is willing to help with asan, that would be great.
Unfortunately we never solved this
Eh, perhaps bad timing, but I was just running valgrind over geary
after a geary crash, and noticed:
https://bugs.webkit.org/show_bug.cgi?id=199295
which I had totally forgotten about.
I don't know whether that's our problem or not, but probably no sense
in worrying about mystery memory
Hi,
Epiphany 3.34 is going to be a pretty crashy release, because we've
developed a memory corruption problem that seems almost impossible to
debug:
https://gitlab.gnome.org/GNOME/epiphany/issues/876
The bug report shows valgrind crashes on startup. I've tried to get a
working asan build
