Created attachment 342038 [details] thread apply all bt full Happened while going back in navigation (and current page was not fully loaded).
I don't see the problem... it's really odd that eolie is creating a new WebKitWebContext during a navigation, but it should have its own separate WebKitFaviconDatabase with its own separate icon database thread. I see an icon database thread is running already, but that should not be concerning because it should be separate.
Eolie does not create a new WebKitWebContext during a navigation, only when creating a new webview. I see WEBKIT_POLICY_DECISION_TYPE_NEW_WINDOW_ACTION in the log so I guess that maybe clicking on the back button happened while current view was creating a new WebView, no?
Ok, I'm no sure when I'm calling set_favicon_database_directory() from a new WebKit2.WebContext(). In Eolie, each webview own a context so I'm able to change cookie manager persistent storage => Profiles like in Firefox.
Disabled feature in Eolie until this one get a fix. https://gitlab.gnome.org/World/eolie/commit/b72b6d3cdc1447f679ef19c9d0dfea6dd10fdf4a
Can confirm that crash comes only from this function: set_favicon_database_directory() Looks like WebKit2GTK really needs this to be called only one time. Not an issue for a normal browser but Eolie was creating a Context per WebView allowing me to have differents cookie managers per WebView (profiles like in Firefox) It's not a blocking issue but it was a cool feature from Eolie: - Go to google.fr => disconnected from google - Go to plus.google.fr => connected to google - etc...