windows linking flakily fails w/ vfork: Resource temporarily unavailable |
||
Issue description
Seeing several of these reported by try-flakes:
FAILED: glibc_x64/ppapi_crash_in_callback_glibc_x86_64.nexe glibc_x64/exe.unstripped/ppapi_crash_in_callback_glibc_x86_64.nexe
C:/b/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe "../../build/toolchain/gcc_link_wrapper.py" --output="glibc_x64/ppapi_crash_in_callback_glibc_x86_64.nexe" --strip="../../native_client/toolchain/win_x86/nacl_x86_glibc/bin/x86_64-nacl-strip.exe" --unstripped-file="glibc_x64/exe.unstripped/ppapi_crash_in_callback_glibc_x86_64.nexe" -- ../../native_client/toolchain/win_x86/nacl_x86_glibc/bin/x86_64-nacl-g++.exe -pthread -m64 -Werror -Wl,-O1 -Wl,--gc-sections -Wl,--fatal-warnings -o "glibc_x64/exe.unstripped/ppapi_crash_in_callback_glibc_x86_64.nexe" -Wl,--start-group @"glibc_x64/ppapi_crash_in_callback_glibc_x86_64.nexe.rsp" -Wl,--end-group
1 [main] collect2 1508 child_info_fork::abort: C:\b\c\b\win\src\native_client\toolchain\win_x86\nacl_x86_glibc\libexec\gcc\x86_64-nacl\4.4.3\cygiconv-2.dll: Loaded to different address: parent(0xC20000) != child(0x6CDC0000)
1 [main] collect2 2480 child_info_fork::abort: C:\b\c\b\win\src\native_client\toolchain\win_x86\nacl_x86_glibc\libexec\gcc\x86_64-nacl\4.4.3\cygiconv-2.dll: Loaded to different address: parent(0xC20000) != child(0x6CDC0000)
1 [main] collect2 5536 child_info_fork::abort: C:\b\c\b\win\src\native_client\toolchain\win_x86\nacl_x86_glibc\libexec\gcc\x86_64-nacl\4.4.3\cygiconv-2.dll: Loaded to different address: parent(0xC20000) != child(0x6CDC0000)
1 [main] collect2 5280 child_info_fork::abort: C:\b\c\b\win\src\native_client\toolchain\win_x86\nacl_x86_glibc\libexec\gcc\x86_64-nacl\4.4.3\cygiconv-2.dll: Loaded to different address: parent(0xC20000) != child(0x6CDC0000)
collect2: vfork: Resource temporarily unavailable
Sample builds:
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/73332
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/73304
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/73295
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/73263
,
Jan 5 2018
This looks like the cygwin issue where they can't handle ASLR and if their desired address is not available they simply fail. This issue is a long-standing issue with the cygwin tools and I don't think there are any plans to fix it. The usual mitigations are awesome suggestions like "reboot". We should probably close this as ExternalDependency, especially if it has stopped happening or is happening "rarely enough".
,
Jan 8 2018
I see no instances of this error in the 400 builds prior to 75672. Closing as WontFix, since ExternalDependency leaves the bug open and we don't expect a viable resolution. |
||
►
Sign in to add a comment |
||
Comment 1 by jbudorick@chromium.org
, Jan 4 2018