On Fri, 2022-07-01 at 10:41 -0500, Tim McConnell via evolution-list
wrote:
> The only thing I get is a banner telling me WebKit crashed
Hi,
yes, that's what I meant.
> It's also how I used to have to exit Evolution is kill webkit
> first, otherwise Evolution would hang
Evo (and/or WebKitGTK) does very weird things on your machine.
I suppose this state can be caught. When you get it into it, get a
backtrace of the evolution process, to see what it is doing (or waiting
on), which can be seen, unless it's an asynchronous operation hidden
somewhere on the heap. The gdb command is like this:
$ gdb --batch --ex "t a a bt" --pid=`pidof evolution` &>bt.txt
Please check the bt.txt for any private information, like passwords,
email addresses, server addresses,... I usually search for "pass" at
least (quotes for clarity only).
Similarly for the corresponding WebKitWebProcess.
> So there was a little improvement?
I'm not sure.
Bye,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
