Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MERP indefinitely hangs on application quit #15646

Closed
Therzok opened this issue Jul 10, 2019 · 0 comments · Fixed by #15715
Closed

MERP indefinitely hangs on application quit #15646

Therzok opened this issue Jul 10, 2019 · 0 comments · Fixed by #15715

Comments

@Therzok
Copy link
Member

@Therzok Therzok commented Jul 10, 2019

Steps to Reproduce

  1. Not available, came in via MERP report: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/942255

Current Behavior

Expected Behavior

On which platforms did you notice this

[*] macOS
[ ] Linux
[ ] Windows

Version Used:

Running on Mono 6.0.0.296 (2019-02/1e9f3bfbc5a) (64-bit)

Stacktrace


Pkilling 0x700008680000 from 0x10bcb85c0
Pkilling 0x700004e23000 from 0x10bcb85c0
Pkilling 0x700002ef0000 from 0x10bcb85c0
Pkilling 0x70000644d000 from 0x10bcb85c0
Pkilling 0x700008c89000 from 0x10bcb85c0
Pkilling 0x7000034f9000 from 0x10bcb85c0
Pkilling 0x700006a56000 from 0x10bcb85c0
Pkilling 0x700003b02000 from 0x10bcb85c0
Pkilling 0x70000512c000 from 0x10bcb85c0
Pkilling 0x70000705f000 from 0x10bcb85c0
Pkilling 0x70000410b000 from 0x10bcb85c0
Pkilling 0x700005735000 from 0x10bcb85c0
Pkilling 0x700007668000 from 0x10bcb85c0
Pkilling 0x700004714000 from 0x10bcb85c0
Pkilling 0x700005d3e000 from 0x10bcb85c0
Pkilling 0x700007c71000 from 0x10bcb85c0
Pkilling 0x700002aea000 from 0x10bcb85c0
Pkilling 0x700008883000 from 0x10bcb85c0
Pkilling 0x70000275e000 from 0x10bcb85c0
Pkilling 0x7000030f3000 from 0x10bcb85c0
Pkilling 0x700006650000 from 0x10bcb85c0
Pkilling 0x7000036fc000 from 0x10bcb85c0
Pkilling 0x700006c59000 from 0x10bcb85c0
Pkilling 0x700003d05000 from 0x10bcb85c0
Pkilling 0x70000532f000 from 0x10bcb85c0
Pkilling 0x700007262000 from 0x10bcb85c0
Pkilling 0x70000430e000 from 0x10bcb85c0
Pkilling 0x700005938000 from 0x10bcb85c0
Pkilling 0x700004917000 from 0x10bcb85c0
Pkilling 0x700005f41000 from 0x10bcb85c0
Pkilling 0x700007e74000 from 0x10bcb85c0
Pkilling 0x70000847d000 from 0x10bcb85c0
Pkilling 0x700004c20000 from 0x10bcb85c0
Pkilling 0x700008a86000 from 0x10bcb85c0
Pkilling 0x700002ced000 from 0x10bcb85c0
Pkilling 0x70000908f000 from 0x10bcb85c0
Pkilling 0x700006853000 from 0x10bcb85c0
Pkilling 0x700006e5c000 from 0x10bcb85c0
Pkilling 0x700003f08000 from 0x10bcb85c0
Pkilling 0x700005532000 from 0x10bcb85c0
Pkilling 0x700007465000 from 0x10bcb85c0
Pkilling 0x700004511000 from 0x10bcb85c0
Pkilling 0x700007a6e000 from 0x10bcb85c0
Pkilling 0x700006144000 from 0x10bcb85c0
Pkilling 0x700008077000 from 0x10bcb85c0
Entering thread summarizer pause from 0x10bcb85c0
Finished thread summarizer pause from 0x10bcb85c0.
2019-07-04 00:11:37.989 VisualStudio[4903:1170325] error: * Assertion at mono-state.c:1017, condition `mem' not met

=================================================================
	Native Crash Reporting
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

=================================================================
	Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0x7fff5986d2c6):0x7fff5986d2b6  ff ff c3 90 90 90 b8 48 01 00 02 49 89 ca 0f 05  .......H...I....
0x7fff5986d2c6  73 08 48 89 c7 e9 87 a1 ff ff c3 55 48 89 e5 41  s.H........UH..A
0x7fff5986d2d6  57 41 56 41 55 41 54 53 48 81 ec 88 00 00 00 4d  WAVAUATSH......M
0x7fff5986d2e6  89 cf 49 89 f4 48 8d 05 76 a2 83 36 48 8b 00 48  ..I..H..v..6H..H

=================================================================
	Native stacktrace:
=================================================================
	0x1087013f8 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_dump_native_crash_info
	0x10869bc75 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_handle_native_crash
	0x7fff5991db5d - /usr/lib/system/libsystem_platform.dylib : _sigtramp
	0x10bc1ab76 - Unknown
	0x7fff597d76a6 - /usr/lib/system/libsystem_c.dylib : abort
	0x105ad8cd0 - /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/libxammac.dylib : _ZL12log_callbackPKcS0_S0_iPv
	0x1089096be - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : monoeg_g_logv_nofree
	0x10890983f - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : monoeg_assertion_message
	0x1088ef5f2 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_summarize_native_state_begin
	0x10883a74d - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_threads_summarize_execute
	0x10870053d - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : sigterm_signal_handler
	0x7fff5991db5d - /usr/lib/system/libsystem_platform.dylib : _sigtramp
	0x108807930 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_debug_add_method
	0x1088f23d0 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_os_cond_timedwait
	0x108859559 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_w32handle_timedwait_signal_handle
	0x108859421 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_w32handle_wait_one
	0x1088909ce - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : ves_icall_System_Threading_Monitor_Monitor_wait
	0x1198887ad - Unknown
	0x11988824b - Unknown
	0x114075e43 - Unknown
	0x11407597b - Unknown
	0x7fff2caecdaf - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec
	0x7fff2caecc35 - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : SendEventToEventTargetWithOptions
	0x7fff2cb09a25 - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ZL29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv
	0x7fff2caede28 - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec
	0x7fff2caecdaf - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec
	0x7fff2cb09f96 - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : SendEventToEventTarget
	0x7fff2caf912f - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ZL20AEPredispatchHandlerPK6AEDescPS_Pv
	0x7fff2ea28397 - /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE : _Z20aeDispatchAppleEventPK6AEDescPS_jPh
	0x7fff2ea27c29 - /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE : _ZL25dispatchEventAndSendReplyPK6AEDescPS_
	0x7fff2ea27b01 - /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE : aeProcessAppleEvent
	0x7fff2caf8e97 - /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : AEProcessAppleEvent
	0x7fff2ae89c7e - /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : _DPSNextEvent
	0x7fff2ae8871f - /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
	0x10ee7b7a7 - /Library/Frameworks/Mono.framework/Versions/6.0.0/lib/libgdk-quartz-2.0.0.dylib : poll_func
	0x10e79b5ab - /Library/Frameworks/Mono.framework/Versions/6.0.0/lib/libglib-2.0.0.dylib : g_main_context_iterate
	0x10e79b85b - /Library/Frameworks/Mono.framework/Versions/6.0.0/lib/libglib-2.0.0.dylib : g_main_loop_run
	0x10e9d2fc2 - /Library/Frameworks/Mono.framework/Versions/6.0.0/lib/libgtk-quartz-2.0.0.dylib : gtk_main
	0x1185a9d28 - Unknown
	0x108eef4bb - Unknown
	0x108eeef93 - Unknown
	0x1085f9409 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_jit_runtime_invoke
	0x1088143e4 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : do_runtime_invoke
	0x1088180bc - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : do_exec_main_checked
	0x10865a33d - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_jit_exec
	0x10865d478 - /Library/Frameworks/Mono.framework/Libraries/libmonosgen-2.0.dylib : mono_main
	0x105a29e65 - /Applications/Visual Studio.app/Contents/MacOS/VisualStudio : main
	0x7fff597323d5 - /usr/lib/system/libdyld.dylib : start
	0x1 - Unknown

=================================================================
	Telemetry Dumper:
=================================================================
Trying to register response after dumping period endedThread 0x10bcb85c0 reported itself.
Crash Reporter has timed out, sending SIGSEGV
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
@alexischr alexischr self-assigned this Jul 16, 2019
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available on the environment's PATH, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Jul 23, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Aug 1, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Aug 1, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Aug 6, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Aug 6, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit to alexischr/mono that referenced this issue Aug 6, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
alexischr added a commit that referenced this issue Aug 9, 2019
* [merp] Use a separate program as the hang supervisor.

Fixes #15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
monojenkins added a commit to monojenkins/mono that referenced this issue Sep 17, 2019
Fixes mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.
marek-safar added a commit that referenced this issue Sep 20, 2019
* [merp] Use a separate program as the hang supervisor.

Fixes #15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.

* Experiment: remove line possibly causing bad compilation under C++
jonpryor added a commit to jonpryor/xamarin-android that referenced this issue Sep 24, 2019
Changes: mono/mono@bfbf823...6d40f13

Context: mono/mono#15646
Context: mono/mono#16689
Context: mono/mono#16759
Context: mono/mono#16824
Context: mono/mono#16918
Context: mono/mono#16974

Improve exception filtering within the debugger.
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Sep 25, 2019
Changes: mono/mono@bfbf823...6d40f13

Context: mono/mono#15646
Context: mono/mono#16689
Context: mono/mono#16759
Context: mono/mono#16824
Context: mono/mono#16918
Context: mono/mono#16974

Improve exception filtering within the debugger.
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Sep 27, 2019
Changes: mono/mono@bfbf823...6d40f13

Context: mono/mono#15646
Context: mono/mono#16689
Context: mono/mono#16759
Context: mono/mono#16824
Context: mono/mono#16918
Context: mono/mono#16974

Improve exception filtering within the debugger.
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Dec 3, 2019
Changes: mono/api-snapshot@fc50bc4...45a61d9

        $ git diff --shortstat fc50bc4f...45a61d93
         22 files changed, 775 insertions(+), 474 deletions(-)

Changes: mono/cecil@a6c8f5e...a6a7f5c

        $ git diff --shortstat a6c8f5e1...a6a7f5c0
         55 files changed, 818 insertions(+), 530 deletions(-)

Changes: mono/corefx@1f87de3...49f1c45

        $ git diff --shortstat e4f7102b...49f1c453
         38 files changed, 1171 insertions(+), 419 deletions(-)

Changes: mono/linker@ebe2a1f...e8d054b

        $ git diff --shortstat ebe2a1f4...e8d054bf
         137 files changed, 5360 insertions(+), 1781 deletions(-)

Changes: mono/mono@8946e49...18920a8

        $ git diff --shortstat 8946e49a...18920a83
         1811 files changed, 47240 insertions(+), 48331 deletions(-)

Changes: xamarin/xamarin-android-api-compatibility@a61271e...50a3c52

        $ git diff --shortstat a61271e0...50a3c52d
         1 file changed, 2 insertions(+), 791 deletions(-)

Fixes: #3619

Context: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1005448
Context: https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems/edit/967582
Context: dotnet/coreclr#26370
Context: dotnet/coreclr#26479
Context: dotnet/corefx#40455
Context: dotnet/corefx#40578
Context: mono/mono#7377
Context: mono/mono#12421
Context: mono/mono#12586
Context: mono/mono#14080
Context: mono/mono#14725
Context: mono/mono#14772
Context: mono/mono#15261
Context: mono/mono#15262
Context: mono/mono#15263
Context: mono/mono#15307
Context: mono/mono#15308
Context: mono/mono#15310
Context: mono/mono#15646
Context: mono/mono#15687
Context: mono/mono#15805
Context: mono/mono#15992
Context: mono/mono#15994
Context: mono/mono#15999
Context: mono/mono#16032
Context: mono/mono#16034
Context: mono/mono#16046
Context: mono/mono#16192
Context: mono/mono#16308
Context: mono/mono#16310
Context: mono/mono#16369
Context: mono/mono#16380
Context: mono/mono#16381
Context: mono/mono#16395
Context: mono/mono#16411
Context: mono/mono#16415
Context: mono/mono#16486
Context: mono/mono#16570
Context: mono/mono#16605
Context: mono/mono#16616
Context: mono/mono#16689
Context: mono/mono#16701
Context: mono/mono#16712
Context: mono/mono#16742
Context: mono/mono#16759
Context: mono/mono#16803
Context: mono/mono#16808
Context: mono/mono#16824
Context: mono/mono#16876
Context: mono/mono#16879
Context: mono/mono#16918
Context: mono/mono#16943
Context: mono/mono#16950
Context: mono/mono#16974
Context: mono/mono#17004
Context: mono/mono#17017
Context: mono/mono#17038
Context: mono/mono#17040
Context: mono/mono#17083
Context: mono/mono#17084
Context: mono/mono#17133
Context: mono/mono#17139
Context: mono/mono#17151
Context: mono/mono#17180
Context: mono/mono#17278
Context: mono/mono#17549
Context: mono/mono#17569
Context: mono/mono#17665
Context: mono/mono#17687
Context: mono/mono#17737
Context: mono/mono#17790
Context: mono/mono#17924
Context: mono/mono#17931
Context: https://github.com/mono/mono/issues/26758
Context: https://github.com/mono/mono/issues/37913
Context: xamarin/xamarin-macios#7005
jonpryor added a commit to xamarin/xamarin-android that referenced this issue Dec 3, 2019
Changes: mono/api-snapshot@fc50bc4...45a61d9

        $ git diff --shortstat fc50bc4f...45a61d93
         22 files changed, 775 insertions(+), 474 deletions(-)

Changes: mono/cecil@a6c8f5e...a6a7f5c

        $ git diff --shortstat a6c8f5e1...a6a7f5c0
         55 files changed, 818 insertions(+), 530 deletions(-)

Changes: mono/corefx@1f87de3...49f1c45

        $ git diff --shortstat e4f7102b...49f1c453
         38 files changed, 1171 insertions(+), 419 deletions(-)

Changes: mono/linker@ebe2a1f...e8d054b

        $ git diff --shortstat ebe2a1f4...e8d054bf
         137 files changed, 5360 insertions(+), 1781 deletions(-)

Changes: mono/mono@8946e49...18920a8

        $ git diff --shortstat 8946e49a...18920a83
         1811 files changed, 47240 insertions(+), 48331 deletions(-)

Changes: xamarin/xamarin-android-api-compatibility@a61271e...50a3c52

        $ git diff --shortstat a61271e0...50a3c52d
         1 file changed, 2 insertions(+), 791 deletions(-)

Fixes: #3619

Context: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1005448
Context: https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems/edit/967582
Context: dotnet/coreclr#26370
Context: dotnet/coreclr#26479
Context: dotnet/corefx#40455
Context: dotnet/corefx#40578
Context: mono/mono#7377
Context: mono/mono#12421
Context: mono/mono#12586
Context: mono/mono#14080
Context: mono/mono#14725
Context: mono/mono#14772
Context: mono/mono#15261
Context: mono/mono#15262
Context: mono/mono#15263
Context: mono/mono#15307
Context: mono/mono#15308
Context: mono/mono#15310
Context: mono/mono#15646
Context: mono/mono#15687
Context: mono/mono#15805
Context: mono/mono#15992
Context: mono/mono#15994
Context: mono/mono#15999
Context: mono/mono#16032
Context: mono/mono#16034
Context: mono/mono#16046
Context: mono/mono#16192
Context: mono/mono#16308
Context: mono/mono#16310
Context: mono/mono#16369
Context: mono/mono#16380
Context: mono/mono#16381
Context: mono/mono#16395
Context: mono/mono#16411
Context: mono/mono#16415
Context: mono/mono#16486
Context: mono/mono#16570
Context: mono/mono#16605
Context: mono/mono#16616
Context: mono/mono#16689
Context: mono/mono#16701
Context: mono/mono#16712
Context: mono/mono#16742
Context: mono/mono#16759
Context: mono/mono#16803
Context: mono/mono#16808
Context: mono/mono#16824
Context: mono/mono#16876
Context: mono/mono#16879
Context: mono/mono#16918
Context: mono/mono#16943
Context: mono/mono#16950
Context: mono/mono#16974
Context: mono/mono#17004
Context: mono/mono#17017
Context: mono/mono#17038
Context: mono/mono#17040
Context: mono/mono#17083
Context: mono/mono#17084
Context: mono/mono#17133
Context: mono/mono#17139
Context: mono/mono#17151
Context: mono/mono#17180
Context: mono/mono#17278
Context: mono/mono#17549
Context: mono/mono#17569
Context: mono/mono#17665
Context: mono/mono#17687
Context: mono/mono#17737
Context: mono/mono#17790
Context: mono/mono#17924
Context: mono/mono#17931
Context: https://github.com/mono/mono/issues/26758
Context: https://github.com/mono/mono/issues/37913
Context: xamarin/xamarin-macios#7005
@Therzok Therzok added this to Needs triage in VS4M Tracker via automation Dec 23, 2019
@Therzok Therzok moved this from Needs triage to Closed in VS4M Tracker Dec 23, 2019
eanova pushed a commit to eanova/runtime that referenced this issue Jan 20, 2020
* [merp] Use a separate program as the hang supervisor.

Fixes mono/mono#15646

macOS does not like signals being sent from the forked supervisor process, possibly towards anywhere but definitely when sent to the parent process. The following message is currently spewed after the supervisor process attempting to send a SIGSEGV to a hanged Mono process:
"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()."

We follow that direction and introduce a new binary that, when available in the mono executable's binary directory, is used to abort the parent process for us.

Commit migrated from mono/mono@2c4b60f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
VS4M Tracker
  
Closed
3 participants
You can’t perform that action at this time.