Shutdown crashes in v120 and above

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Shutdown crashes in v120 and above

Postby ssaraf » Wed Mar 27, 2024 2:15 am

Hi, we see a lot of shutdown crashes in v116, v120 & v121. The call stack is similar to

[ 00 ] logging::LogMessage::~LogMessage() ( logging.cc:937 )
[ 01 ] static void CefFrameImpl::OnDisconnect(CefFrameImpl::DisconnectReason) ( frame_impl.cc:609 )
[ 02 ] mojo::InterfaceEndpointClient::NotifyError(std::__Cr::optional<mojo::DisconnectReason> const &) ( interface_endpoint_client.cc:739 )
[ 03 ] static void base::internal::Invoker<base::internal::BindState<void (mojo::internal::MultiplexRouter::*)(bool),base::internal::UnretainedWrapper<mojo::internal::MultiplexRouter,base::unretained_traits::MayNotDangle,0>,bool>,void ()>::RunOnce(class base::internal::BindStateBase *) ( bind_internal.h:920 )
[ 04 ] static void base::internal::Invoker<base::internal::BindState<void (mojo::Connector::*)(const char *, unsigned int),base::internal::UnretainedWrapper<mojo::Connector,base::unretained_traits::MayNotDangle,0>,base::internal::UnretainedWrapper<const char,base::unretained_traits::MayNotDangle,0> >,void (unsigned int)>::Run(class base::internal::BindStateBase *, unsigned int) ( bind_internal.h:933 )
[ 05 ] void base::internal::Invoker<base::internal::BindState<void (*)(const base::RepeatingCallback<void (unsigned int)> &, unsigned int, const mojo::HandleSignalsState &),base::RepeatingCallback<void (unsigned int)> >,void (unsigned int, const mojo::HandleSignalsState &)>::Run(class base::internal::BindStateBase *, unsigned int, const struct mojo::HandleSignalsState & const) ( bind_internal.h:933 )
[ 06 ] static void mojo::SimpleWatcher::OnHandleReady(int, unsigned int, const struct mojo::HandleSignalsState & const) ( simple_watcher.cc:278 )


Do we have any workaround or solution for the same?
ssaraf
Techie
 
Posts: 32
Joined: Mon Nov 09, 2020 2:18 am

Re: Shutdown crashes in v120 and above

Postby ndesktop » Wed Mar 27, 2024 2:55 am

Try to run with --enable-logging and check what the (probable) LOG(ERROR) prints.
Most likely the frame OnDisconnect receives a reason different than DisconnectReason::BROWSER_FRAME_DETACHED is still navigating and attempts to call CefFrameImpl::ConnectBrowserFrame, but without a debug it's hard to tell.

I would try to call browser->StopLoad() for each browser still alive at the moment of shutdown.
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: Shutdown crashes in v120 and above

Postby magreenblatt » Wed Mar 27, 2024 10:16 am

magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Shutdown crashes in v120 and above

Postby ndesktop » Wed Mar 27, 2024 12:22 pm

I have noticed the disconnect crash some time ago. My solution was to change from FATAL to ERROR as suggested as one of the possible solutions (but that inside of chromium src). Did not saw the crash since.
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: Shutdown crashes in v120 and above

Postby ssaraf » Thu Apr 04, 2024 6:37 am

Do we have any workaround/solution for this crash?
ssaraf
Techie
 
Posts: 32
Joined: Mon Nov 09, 2020 2:18 am


Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 235 guests