Bug#999358: libwebkit2gtk-4.0-37: Upgrade from 2.30.1-1~bpo10+1 to 2.34.1-1~deb10u1 crashes evolution with "std::bad_alloc"

Alberto Garcia berto at igalia.com
Thu Nov 11 22:01:05 GMT 2021

On Thu, Nov 11, 2021 at 02:27:36PM +0100, Norbert Berzen wrote:
> > Better if you can install the debug packages from this repository:
> > 
> > deb http://debug.mirrors.debian.org/debian-debug/ buster-debug main
> The repo you mentioned does only contain "libwebkit2gtk-4.0-37-dbgsym"
> of old version "2.32.4-1~deb10u1"

Ah right, there are no debug packages for security updates... :-S

> > If you can send me a backtrace with gdb I'd appreciate it.
> Just I see the exception is comming out of "libjavascriptcoregtk"
> instead of "libwebkit2gtk", but anyway the problem remains:
> Here the backtrace follows ...
> #6  0x00007ffff2749f1f in std::__throw_bad_alloc () at
> /home/norbert/DEVEL/gcc-x.y.z/gcc-10.2.0/libstdc++-
> v3/src/c++11/functexcept.cc:54
> #7  0x00007ffff103a53c in
> WTF::FileSystemImpl::pathByAppendingComponent(WTF::String const&,
> WTF::String const&) () from /lib/x86_64-linux-gnu/libjavascriptcoregtk-
> 4.0.so.18

Ok, this is a bad allocation triggered by pathByAppendingComponent(),
it seems very unlikely that you run out of memory doing this
operation, maybe one of the parameters is corrupted... it would be
useful to see the rest of the backtrace.

The problem is that I cannot reproduce it myself... do you need to
follow any steps? Does the Evolution window appear, are you able to
see anything before the crash?


More information about the Pkg-webkit-maintainers mailing list