`dotnet` exits with exit code `139` on linux, with a core file dumped #68393

mangod9 · 2022-04-22T14:48:08Z

Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1732324&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=961bb5d4-39cc-55d0-23ed-82f28319785b

Configuration: Build Browser wasm Linux Release WasmBuildTests

Build process exited with non-zero exit code: 139

output:
        Binlog path: /datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog
        Running /datadisks/disk1/work/B324093F/p/sdk-no-workload/dotnet publish -p:WasmBuildOnlyAfterPublish=true  /p:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build /p:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk  /p:Configuration=Release /bl:"/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog" /nologo /fl /flp:"v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log" /v:minimal  
        WorkingDirectory: /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt
        Setting environment variables for execution:
        	EMSDK_PATH = /datadisks/disk1/work/B324093F/p/build/emsdk
        	DOTNET_INSTALL_DIR = /datadisks/disk1/work/B324093F/p/sdk-no-workload
        	DOTNET_MULTILEVEL_LOOKUP = 0
        	DOTNET_SKIP_FIRST_TIME_EXPERIENCE = 1
        	_WasmStrictVersionMatch = true
        	MSBuildSDKsPath = 
        	PATH = /datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/xharness-cli:/datadisks/disk1/work/B324093F/p/dotnet-cli:/datadisks/disk1/work/B324093F/p/build/emsdk/node/14.18.2_64bit/bin:/datadisks/disk1/work/B324093F/p/chrome-linux:/datadisks/disk1/work/B324093F/p/chromedriver_linux64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
        	WasmNativeStrip = false
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/MSBuild.dll /fl /nologo -maxcpucount -property:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build -property:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk -property:Configuration=Release -p:WasmBuildOnlyAfterPublish=true -restore -target:Publish -verbosity:m /v:minimal /bl:/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog /flp:v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log ./rebuild_noop_Release.csproj
        [zr4xcvzb.3zt]   Determining projects to restore...
        [zr4xcvzb.3zt]   Restored /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj (in 99 ms).
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(216,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj]

Build	Kind	Start Time
1731369	Rolling	2022-21-04
1732324	Rolling	2022-22-04

The text was updated successfully, but these errors were encountered:

dotnet-issue-labeler · 2022-04-22T14:48:11Z

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

ghost · 2022-04-25T18:08:23Z

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1732324&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=961bb5d4-39cc-55d0-23ed-82f28319785b

Configuration: Build Browser wasm Linux Release WasmBuildTests

Build process exited with non-zero exit code: 139

output:
        Binlog path: /datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog
        Running /datadisks/disk1/work/B324093F/p/sdk-no-workload/dotnet publish -p:WasmBuildOnlyAfterPublish=true  /p:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build /p:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk  /p:Configuration=Release /bl:"/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog" /nologo /fl /flp:"v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log" /v:minimal  
        WorkingDirectory: /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt
        Setting environment variables for execution:
        	EMSDK_PATH = /datadisks/disk1/work/B324093F/p/build/emsdk
        	DOTNET_INSTALL_DIR = /datadisks/disk1/work/B324093F/p/sdk-no-workload
        	DOTNET_MULTILEVEL_LOOKUP = 0
        	DOTNET_SKIP_FIRST_TIME_EXPERIENCE = 1
        	_WasmStrictVersionMatch = true
        	MSBuildSDKsPath = 
        	PATH = /datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/xharness-cli:/datadisks/disk1/work/B324093F/p/dotnet-cli:/datadisks/disk1/work/B324093F/p/build/emsdk/node/14.18.2_64bit/bin:/datadisks/disk1/work/B324093F/p/chrome-linux:/datadisks/disk1/work/B324093F/p/chromedriver_linux64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
        	WasmNativeStrip = false
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/MSBuild.dll /fl /nologo -maxcpucount -property:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build -property:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk -property:Configuration=Release -p:WasmBuildOnlyAfterPublish=true -restore -target:Publish -verbosity:m /v:minimal /bl:/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog /flp:v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log ./rebuild_noop_Release.csproj
        [zr4xcvzb.3zt]   Determining projects to restore...
        [zr4xcvzb.3zt]   Restored /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj (in 99 ms).
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(216,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj]

Build	Kind	Start Time
1731369	Rolling	2022-21-04
1732324	Rolling	2022-22-04

Author:	mangod9
Assignees:	-
Labels:	`arch-wasm`, `blocking-clean-ci`
Milestone:	-

ghost · 2022-04-25T18:08:45Z

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1732324&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=961bb5d4-39cc-55d0-23ed-82f28319785b

Configuration: Build Browser wasm Linux Release WasmBuildTests

Build process exited with non-zero exit code: 139

output:
        Binlog path: /datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog
        Running /datadisks/disk1/work/B324093F/p/sdk-no-workload/dotnet publish -p:WasmBuildOnlyAfterPublish=true  /p:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build /p:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk  /p:Configuration=Release /bl:"/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog" /nologo /fl /flp:"v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log" /v:minimal  
        WorkingDirectory: /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt
        Setting environment variables for execution:
        	EMSDK_PATH = /datadisks/disk1/work/B324093F/p/build/emsdk
        	DOTNET_INSTALL_DIR = /datadisks/disk1/work/B324093F/p/sdk-no-workload
        	DOTNET_MULTILEVEL_LOOKUP = 0
        	DOTNET_SKIP_FIRST_TIME_EXPERIENCE = 1
        	_WasmStrictVersionMatch = true
        	MSBuildSDKsPath = 
        	PATH = /datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/sdk-no-workload:/datadisks/disk1/work/B324093F/p/xharness-cli:/datadisks/disk1/work/B324093F/p/dotnet-cli:/datadisks/disk1/work/B324093F/p/build/emsdk/node/14.18.2_64bit/bin:/datadisks/disk1/work/B324093F/p/chrome-linux:/datadisks/disk1/work/B324093F/p/chromedriver_linux64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
        	WasmNativeStrip = false
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/MSBuild.dll /fl /nologo -maxcpucount -property:WasmBuildSupportDir=/datadisks/disk1/work/B324093F/p/build -property:EMSDK_PATH=/datadisks/disk1/work/B324093F/p/build/emsdk -property:Configuration=Release -p:WasmBuildOnlyAfterPublish=true -restore -target:Publish -verbosity:m /v:minimal /bl:/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog /flp:v:diag,LogFile=/datadisks/disk1/work/B324093F/w/AB500975/uploads/xharness-output/logs/zr4xcvzb.3zt/rebuild_noop_Release.binlog.log ./rebuild_noop_Release.csproj
        [zr4xcvzb.3zt]   Determining projects to restore...
        [zr4xcvzb.3zt]   Restored /datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj (in 99 ms).
        [zr4xcvzb.3zt] /datadisks/disk1/work/B324093F/p/sdk-no-workload/sdk/7.0.100-preview.5.22220.23/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(216,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [/datadisks/disk1/work/B324093F/w/AB500975/e/zr4xcvzb.3zt/rebuild_noop_Release.csproj]

Build	Kind	Start Time
1731369	Rolling	2022-21-04
1732324	Rolling	2022-22-04

Author:	mangod9
Assignees:	-
Labels:	`arch-wasm`, `blocking-clean-ci`, `area-Infrastructure-mono`
Milestone:	-

radical · 2022-04-25T18:10:30Z

We have been seeing dotnet restore exiting with 139 frequently in the last few weeks, in runtime*, and perf pipelines.
@rainersigwald Any idea if something broke recently?

rainersigwald · 2022-04-25T20:19:10Z

Nothing I know of . . .

jakobbotsch · 2022-05-05T20:41:49Z

Tracked at dotnet/msbuild#7596

jakobbotsch · 2022-05-06T13:28:32Z

We have seen this failure twice in rolling builds this week, in https://dev.azure.com/dnceng/public/_build/results?buildId=1746930&view=results and https://dev.azure.com/dnceng/public/_build/results?buildId=1752379&view=results.
Can we help with the investigation somehow? e.g. by trying to run the same build in a loop on our own machines?

jkotas · 2022-05-10T17:27:16Z

This is very likely duplicate of #68443 that was just fixed in dotnet/runtime. We need to get .NET SDK with the fix to make this failure go away.

lewing · 2022-06-09T16:31:02Z

This is blocked on #70117

radical · 2022-07-06T14:56:06Z

I'm still seeing regular instances of this on the perf pipeline.

mangod9 · 2022-07-06T15:04:22Z

Is there a dump available with the failure?

radical · 2022-07-06T15:26:55Z

core file.

mangod9 · 2022-07-06T15:46:43Z

This looks to be an OpenSSL shutdown issue. Adding @bartonjs @wfurt since we have seen something similar a few weeks ago, and it was mentioned that this was a wont fix on Ubuntu 18.04. Perhaps we should update the OS for helix?

S Thread Id: 0x5f26 (0)
TEB information is not available so a stack size of 0xFFFF is assumed
Current frame: libpthread_2_27!__pthread_rwlock_wrlock + 0x12
Child-SP         RetAddr          Caller, Callee
00007F00FCFF7D50 00007f42306f8c59 libcrypto_so_1!CRYPTO_THREAD_write_lock + 0x9, calling libcrypto_so_1!pthread_rwlock_wrlock$plt
00007F00FCFF7D60 00007f42306ba2d3 libcrypto_so_1!RAND_get_rand_method + 0x33, calling libcrypto_so_1!CRYPTO_THREAD_write_lock
00007F00FCFF7D80 00007f42306ba5b0 libcrypto_so_1!RAND_bytes + 0x10, calling libcrypto_so_1!RAND_get_rand_method
00007F00FCFF7DA0 00007f423067775f libcrypto_so_1!EVP_MD_CTX_ctrl + 0x132f, calling libcrypto_so_1!RAND_bytes
00007F00FCFF7DD0 00007f4230685d57 libcrypto_so_1!EVP_CIPHER_CTX_ctrl + 0x17
00007F00FCFF7DE0 00007f4230a43814 libssl_so_1!SSL_in_before + 0x13bd4, calling libssl_so_1!EVP_CIPHER_CTX_ctrl$plt
00007F00FCFF7E40 00007f4230a42ebe libssl_so_1!SSL_in_before + 0x1327e, calling libssl_so_1!EVP_PKEY_CTX_free$plt
00007F00FCFF7E90 00007f4230a439a3 libssl_so_1!SSL_in_before + 0x13d63, calling libssl_so_1!SSL_in_before + 0x131f0
00007F00FCFF7F30 00007f4230a3562a libssl_so_1!SSL_in_before + 0x59ea
00007F00FCFF8010 00007f4230a1c4e4 libssl_so_1!SSL_do_handshake + 0x54
00007F00FCFF8020 00007f42306714bd libcrypto_so_1!ERR_clear_error + 0xd, calling libcrypto_so_1!ERR_get_state
00007F00FCFF8050 00007f4230ca2bf5 libSystem_Security_Cryptography_Native_OpenSsl!CryptoNative_SslDoHandshake + 0x25 [/__w/1/s/src/native/libs/System.Security.Cryptography.Native/pal_ssl.c:550]
00007F00FCFF8440 00007f423e6f1b68 (MethodDesc 00007f423f2fc740 + 0x858 /home/helixbot/work/BF9E0A05/p/dotnet/shared/Microsoft.NETCore.App/7.0.0-preview.6.22329.5/System.Net.Security.dll!Unknown), calling 00007f423f66c300
00007F00FCFF8670 00007f423e6f4397 (MethodDesc 00007f423f323570 + 0x27 /home/helixbot/work/BF9E0A05/p/dotnet/shared/Microsoft.NETCore.App/7.0.0-preview.6.22329.5/System.Private.CoreLib.dll!Unknown), calling 00007f423f66ab40
00007F00FCFF8760 00007f423e6f40aa (MethodDesc 00007f423f3235a0 + 0x1a /home/helixbot/work/BF9E0A05/p/dotnet/shared/Microsoft.NETCore.App/7.0.0-preview.6.22329.5/System.Private.CoreLib.dll!Unknown), calling 00007f423f66c228
00007F00FCFF8780 00007f423e6f22b2 (MethodDesc 00007f423f2fe460 + 0x452 /home/helixbot/work/BF9E0A05/p/dotnet/shared/Microsoft.NETCore.App/7.0.0-preview.6.22329.5/System.Net.Security.dll!Unknown), calling 00007f423f66c1f8
00007F00FCFF88D0 00007f423e6f4073 (MethodDesc 00007f423f3204f8 + 0x23 /home/helixbot/work/BF9E0A05/p/dotnet/shared/Microsoft.NETCore.App/7.0.0-preview.6.22329.5/System.Private.CoreLib.dll!Unknown), calling 00007f423f66abb8
00007F00FCFF8B90 00007f42b75be487 libcoreclr!CallDescrWorkerInternal + 0x7c [/__w/1/s/src/coreclr/pal/inc/unixasmmacrosamd64.inc:839]
00007F00FCFF8BB0 00007f42b73f527e libcoreclr!DispatchCallSimple + 0xfe, calling libcoreclr!CallDescrWorkerInternal [/__w/1/s/src/coreclr/pal/inc/unixasmmacrosamd64.inc:781]
00007F00FCFF8C40 00007f42b740d342 libcoreclr!ThreadNative::KickOffThread_Worker + 0x92 [/__w/1/s/src/coreclr/vm/comsynchronizable.cpp:15732480], calling libcoreclr!DispatchCallSimple [/__w/1/s/src/coreclr/vm/callhelpers.cpp:171]
00007F00FCFF8C70 00007f42b732eef9 libcoreclr!Frame::Push + 0x19, calling libcoreclr!_tls_get_addr$plt
00007F00FCFF8C90 00007f42b73bd98a libcoreclr!ManagedThreadBase_DispatchOuter + 0x14a
00007F00FCFF8DB0 00007f42b73bdf8d libcoreclr!ManagedThreadBase::KickOff + 0x2d, calling libcoreclr!ManagedThreadBase_DispatchOuter [/__w/1/s/src/coreclr/vm/threads.cpp:7457]
00007F00FCFF8DE0 00007f42b740d417 libcoreclr!ThreadNative::KickOffThread + 0xb7 [/__w/1/s/src/coreclr/vm/comsynchronizable.cpp:230], calling libcoreclr!ManagedThreadBase::KickOff [/__w/1/s/src/coreclr/vm/threads.cpp:7583]
00007F00FCFF8E40 00007f42b77499ae libcoreclr!CorUnix::CPalThread::ThreadEntry + 0x24e
00007F00FCFF8EF0 00007f42b87556db libpthread_2_27!start_thread + 0xdb [/build/glibc-uZu3wS/glibc-2.27/nptl/pthread_create.c:463]
00007F00FCFF8FB0 00007f42b793b61f libc_2_27!_GI___clone + 0x3f [/build/glibc-uZu3wS/glibc-2.27/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:97]

radical · 2022-07-06T17:15:56Z

This looks to be an OpenSSL shutdown issue. Adding @bartonjs @wfurt since we have seen something similar a few weeks ago, and it was mentioned that this was a wont fix on Ubuntu 18.04. Perhaps we should update the OS for helix?

@DrewScoggins this is for the perf pipeline. We hit this issue a few times a day, with dotnet restore, or dotnet build just exiting with exit code 139. Can we update the OS as suggested here?

@mangod9 can we confirm that it is the same issue?

mangod9 · 2022-07-06T18:05:56Z

@mangod9 can we confirm that it is the same issue?

will need to defer to @bartonjs and @wfurt for this.

bartonjs · 2022-07-06T18:10:28Z

If it's only happening on Ubuntu 18.04, then it's almost certainly that known problem.

wfurt · 2022-07-07T16:59:11Z

The question is what we are in middle of SSL when the process is shutting down. Disposing SslStream properly before shutdown should fix it, right @bartonjs ?

radical · 2022-07-21T16:04:40Z

@DrewScoggins can you we update to a newer version, from Ubuntu 18.04?

We are seeing this issue on jobs for main too, for example - https://github.com/dotnet/runtime/pull/72275/checks?check_run_id=7451991854 . cc @akoeplinger @radekdoulik Can we update the image there?

cc @lewing

radical · 2022-07-25T19:36:14Z

This is hit frequently, especially on the dotnet-runtime-perf pipeline.

radical · 2022-08-04T01:07:05Z

This looks to be an OpenSSL shutdown issue. Adding @bartonjs @wfurt since we have seen something similar a few weeks ago, and it was mentioned that this was a wont fix on Ubuntu 18.04. Perhaps we should update the OS for helix?

@DrewScoggins this is for the perf pipeline. We hit this issue a few times a day, with dotnet restore, or dotnet build just exiting with exit code 139. Can we update the OS as suggested here?

ping @DrewScoggins

bartonjs · 2022-08-04T17:19:59Z

FWIW, there's now a bug on Ubuntu's side (https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100). Per the comments there, a fix has been built; hopefully it flows out to general distribution and we can stop having the position of "yeah, we get crashes on Ubuntu 18.04..."

radical · 2022-08-17T18:03:50Z

FWIW, there's now a bug on Ubuntu's side (bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100). Per the comments there, a fix has been built; hopefully it flows out to general distribution and we can stop having the position of "yeah, we get crashes on Ubuntu 18.04..."

🤞 We hit this pretty regularly on the dotnet-runtime-perf pipeline.

mdh1418 · 2022-10-03T17:20:35Z

I think this was hit again on an unrelated PR https://dev.azure.com/dnceng-public/public/_build/results?buildId=36771&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=b731ef43-7f67-5a47-0aca-433fa8d3212b

dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 22, 2022

mangod9 added the wasm-aot-test WebAssembly AOT Test label Apr 22, 2022

jeffschwMSFT added the area-VM-meta-mono label Apr 22, 2022

mangod9 added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Apr 25, 2022

runfoapp bot mentioned this issue Apr 25, 2022

Infrastructure - Status/Health #702

Closed

radical added arch-wasm WebAssembly architecture and removed untriaged New issue has not been triaged by the area owner area-VM-meta-mono wasm-aot-test WebAssembly AOT Test labels Apr 25, 2022

radical added the area-Infrastructure-mono label Apr 25, 2022

jkotas mentioned this issue Apr 28, 2022

Delete .NET Framework ildasm headers from test sources #68614

Merged

jakobbotsch mentioned this issue May 5, 2022

CI: wasm.build.tests.satelliteassembliestests.resourcesfrommainassembly CI failure on Linux #68773

Closed

jakobbotsch added the tracking-external-issue The issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly label May 5, 2022

lewing assigned radical Jun 9, 2022

lewing added the blocked Issue/PR is blocked on something - see comments label Jun 9, 2022

radical removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Jun 10, 2022

radical changed the title ~~CI Test Failure: Wasm.Build.Tests.MainWithArgsTests.NonAsyncMainWithArgs~~ dotnet exits with exit code 139 on linux, with a core file dumped Jun 10, 2022

agocke mentioned this issue Jun 15, 2022

Upgrade SDK to Preview 5 #70117

Merged

lambdageek added this to the 7.0.0 milestone Jul 6, 2022

radical modified the milestones: 7.0.0, 8.0.0 Aug 4, 2022

ghost added the untriaged New issue has not been triaged by the area owner label Aug 4, 2022

jeffschwMSFT removed the untriaged New issue has not been triaged by the area owner label Aug 4, 2022

dougbu mentioned this issue Aug 30, 2022

Update SDK dotnet/aspnetcore#43028

Merged

lewing mentioned this issue Sep 14, 2022

Segmentation fault (SIGSEGV) on LinuxBionic #75502

Open

lewing closed this as completed Jul 25, 2023

ghost locked as resolved and limited conversation to collaborators Aug 25, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`dotnet` exits with exit code `139` on linux, with a core file dumped #68393

`dotnet` exits with exit code `139` on linux, with a core file dumped #68393

mangod9 commented Apr 22, 2022 •

edited by radical

Loading

dotnet-issue-labeler bot commented Apr 22, 2022

ghost commented Apr 25, 2022

ghost commented Apr 25, 2022

radical commented Apr 25, 2022

rainersigwald commented Apr 25, 2022

jakobbotsch commented May 5, 2022

jakobbotsch commented May 6, 2022

jkotas commented May 10, 2022

lewing commented Jun 9, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

bartonjs commented Jul 6, 2022

wfurt commented Jul 7, 2022

radical commented Jul 21, 2022

radical commented Jul 25, 2022

radical commented Aug 4, 2022

bartonjs commented Aug 4, 2022

radical commented Aug 17, 2022

mdh1418 commented Oct 3, 2022

dotnet exits with exit code 139 on linux, with a core file dumped #68393

dotnet exits with exit code 139 on linux, with a core file dumped #68393

Comments

mangod9 commented Apr 22, 2022 • edited by radical Loading

dotnet-issue-labeler bot commented Apr 22, 2022

ghost commented Apr 25, 2022

ghost commented Apr 25, 2022

radical commented Apr 25, 2022

rainersigwald commented Apr 25, 2022

jakobbotsch commented May 5, 2022

jakobbotsch commented May 6, 2022

jkotas commented May 10, 2022

lewing commented Jun 9, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

radical commented Jul 6, 2022

mangod9 commented Jul 6, 2022

bartonjs commented Jul 6, 2022

wfurt commented Jul 7, 2022

radical commented Jul 21, 2022

radical commented Jul 25, 2022

radical commented Aug 4, 2022

bartonjs commented Aug 4, 2022

radical commented Aug 17, 2022

mdh1418 commented Oct 3, 2022

`dotnet` exits with exit code `139` on linux, with a core file dumped #68393

`dotnet` exits with exit code `139` on linux, with a core file dumped #68393

mangod9 commented Apr 22, 2022 •

edited by radical

Loading