You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you get an error like Error: Returning from a request handler without responding or attaching an abort handler is forbidden! that is fine can fix it, but it also prints terminate called without an active exception then cpu goes to 100% for process systemd-coredum and the node process won't exit with ctr+c for like 10 seconds then Aborted (core dumped), it should just immediately exit the program
The text was updated successfully, but these errors were encountered:
That message should probably be cleaned up. Maybe std::terminate() is not as direct as std::abort(). But you don't want std::exit() because it is supposed to be a critical error.
I think this not not a bug but just your coredump taking a long time? We call std::terminate on invalid use, and this calls std::abort which causes a coredump on some systems. I think this is fine, because calling std::exit would be just a normal program termination. IMO there is nothing to fix here, so closing for now.
If you get an error like
Error: Returning from a request handler without responding or attaching an abort handler is forbidden!
that is fine can fix it, but it also printsterminate called without an active exception
then cpu goes to 100% for processsystemd-coredum
and the node process won't exit with ctr+c for like 10 seconds thenAborted (core dumped)
, it should just immediately exit the programThe text was updated successfully, but these errors were encountered: