…atforms The macOS-only `std::_Exit(0)` block in OnExit() was added to dodge a wxWebSessionURLSession dtor bug under wx 3.3.2. Turns out the Linux backend (wxWebSessionCURL, wx 3.2.6) hits the same class of shutdown crash: its dtor calls curl_multi_cleanup, libcurl invokes the registered socket callback (wxWebSessionCURL::SocketCallback) to drop tracked sockets, and that callback dereferences session state the dtor's earlier steps have already torn down. wxASSERT fires, wxFatalSignalHandler raise(SIGABRT)s. Verified with a debug-symbol Flatpak + gdb on a user-supplied core, fully symbolicated: amule-project#19 main amule-gui.cpp:98 amule-project#18 wxEntry wx/init.cpp:500 amule-project#17 wxEntryCleanup wx/init.cpp:205 amule-project#16 wxModule::CleanUpModules wx/module.cpp:191 amule-project#15 wxModule::DoCleanUpModules wx/module.cpp:200 amule-project#14 wxRefCounterMT::DecRef wxWebSession::Close wx/webrequest.cpp:1074 amule-project#13 wxWebSessionCURL::~wxWebSessionCURL wx/webrequest_curl.cpp:932 amule-project#12 wxWebSessionCURL::~wxWebSessionCURL wx/webrequest_curl.cpp:929 amule-project#11-amule-project#6 libcurl curl_multi_cleanup amule-project#5 wxWebSessionCURL::SocketCallback wx/webrequest_curl.cpp:1047 amule-project#4 raise() amule-project#3 wxFatalSignalHandler wx/unix/utilsunx.cpp:1523 #0 abort Same justification used for the macOS guard applies on every platform: by this point in OnExit we have saved state, joined threads, and flushed logs -- nothing aMule-owned remains to clean up. _Exit bypasses atexit and static destructors uniformly, so the buggy wx dtor never runs and the process terminates cleanly. Remove this once the upstream wx fix lands in a release we depend on. Reported in amule-project#18.

Uh oh!

2.4.0 @ 0023527b: closing last search result tab terminates aMule #18

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions