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.

Sign up for GitHub

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

Jump to bottom

Segmentation fault in "Testing in COMBINE_RESULTS", later "Caught fatal signal - signo:11 code:1 errno:0" #216

Open
achimmihca opened this issue Mar 16, 2023 · 11 comments
Open

Segmentation fault in "Testing in COMBINE_RESULTS", later "Caught fatal signal - signo:11 code:1 errno:0" #216

achimmihca opened this issue Mar 16, 2023 · 11 comments
Labels
bug Something isn't working

Comments

@achimmihca
Copy link

achimmihca commented Mar 16, 2023 •
edited
Loading

Bug description

Unity crashes in my test build for Linux when shutting down.
The build finishes fine for Android and iOS.

Not sure if this is related to Unity or the GitHub Action.
Log file is attached.

Interestingly, the tests seem to finish mostly. Then there is a "Segmentation fault" but it continues

2023-03-16T10:19:55.6642432Z ###########################
2023-03-16T10:19:55.6642687Z #   Testing in COMBINE_RESULTS  #
2023-03-16T10:19:55.6642903Z ###########################
2023-03-16T10:19:55.6642910Z 
2023-03-16T12:07:07.1370084Z Segmentation fault (core dumped)
2023-03-16T12:07:07.1480815Z Unity Editor version:    2022.2.10f1 (bcebec703747)
2023-03-16T12:07:07.1485026Z Branch:                  2022.2/staging
2023-03-16T12:07:07.1485841Z Build type:              Release
2023-03-16T12:07:07.1486389Z Batch mode:              YES
2023-03-16T12:07:07.1486929Z System name:             Linux
2023-03-16T12:07:07.1487840Z Distro version:          game-ci/unity-builder#41-Ubuntu SMP Fri Feb 10 19:59:45 UTC 2023
2023-03-16T12:07:07.1531039Z Kernel version:          5.15.0-1034-azure
2023-03-16T12:07:07.1531633Z Architecture:            x86_64
2023-03-16T12:07:07.1532207Z Available memory:        6943 MB
2023-03-16T12:07:07.1533045Z [Licensing::Module] Trying to connect to existing licensing client channel...

...

Later, it crashes completely:

2023-03-16T12:07:07.1939887Z Batchmode quit successfully invoked - shutting down!
2023-03-16T12:07:07.1940587Z Curl error 42: Callback aborted
2023-03-16T12:07:07.1941291Z [Licensing::IpcConnector] License Notification channel disconnected successfully.
2023-03-16T12:07:07.1942182Z [Licensing::IpcConnector] License Client channel disconnected successfully.
2023-03-16T12:07:07.1943221Z �[40m�[32minfo�[39m�[22m�[49m: Microsoft.Hosting.Lifetime[0]
2023-03-16T12:07:07.1943958Z       Application is shutting down...
2023-03-16T12:07:07.1944887Z �[40m�[32minfo�[39m�[22m�[49m: Unity.ILPP.Runner.PostProcessingAssemblyLoadContext[0]
2023-03-16T12:07:07.1945712Z       ALC ILPP context 1 is unloading
2023-03-16T12:07:07.1946537Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x4140
2023-03-16T12:07:07.1947380Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1948300Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1949302Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1950421Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1951282Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1952104Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec
2023-03-16T12:07:07.1952937Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x7f5f48000fec

[above and below message repeated a lot]

2023-03-16T12:07:10.3359798Z Caught fatal signal - signo:11 code:128 errno:0 addr:(nil)
2023-03-16T12:07:10.3360137Z Caught fatal signal - signo:11 code:128 errno:0 addr:(nil)
2023-03-16T12:07:10.3360521Z Caught fatal signal - signo:11 code:128 errno:0 addr:(nil)
2023-03-16T12:07:10.3360865Z Caught fatal signal - signo:11 code:128 errno:0 addr:(nil)
2023-03-16T12:07:10.3361107Z Unexpected exit code 139
2023-03-16T12:07:10.3361124Z 
2023-03-16T12:07:10.3361354Z ###########################
2023-03-16T12:07:10.3361618Z #    COMBINE_RESULTS Results    #
2023-03-16T12:07:10.3361835Z ###########################
2023-03-16T12:07:10.3361908Z 
2023-03-16T12:07:10.3362371Z chmod: cannot access '/github/workspace/CodeCoverage': No such file or directory
2023-03-16T12:07:10.3362814Z Changing to "/github/workspace/_activate-license" directory.
2023-03-16T12:07:10.3363187Z /github/workspace/_activate-license /github/workspace
2023-03-16T12:07:10.3363402Z /github/workspace
2023-03-16T12:07:10.3363410Z 
2023-03-16T12:07:10.3363624Z ###########################
2023-03-16T12:07:10.3363848Z #         Failure         #
2023-03-16T12:07:10.3364061Z ###########################

How to reproduce

Expected behavior

The build should finish cleanly.

Additional details

See attached log file

build-log.log
@achimmihca achimmihca added the bug Something isn't working label Mar 16, 2023
@achimmihca
Copy link
Author

Maybe this is related ?
https://forum.unity.com/threads/caught-fatal-signal-signo-11-code-1-errno-0.931848/

@achimmihca
Copy link
Author

achimmihca commented Mar 16, 2023 •
edited
Loading

I have a slightly more helpful error message when doing the build with Windows target platform:

2023-03-16T13:10:30.3442240Z Batchmode quit successfully invoked - shutting down!
2023-03-16T13:10:30.3442849Z Curl error 42: Callback aborted
2023-03-16T13:10:30.3443549Z [Licensing::IpcConnector] License Notification channel disconnected successfully.
2023-03-16T13:10:30.3444339Z [Licensing::IpcConnector] License Client channel disconnected successfully.
2023-03-16T13:10:30.3445129Z �[40m�[32minfo�[39m�[22m�[49m: Microsoft.Hosting.Lifetime[0]
2023-03-16T13:10:30.3445768Z       Application is shutting down...
2023-03-16T13:10:30.3446600Z �[40m�[32minfo�[39m�[22m�[49m: Unity.ILPP.Runner.PostProcessingAssemblyLoadContext[0]
2023-03-16T13:10:30.3447331Z       ALC ILPP context 1 is unloading
2023-03-16T13:10:30.3448031Z Caught fatal signal - signo:11 code:1 errno:0 addr:0x80
2023-03-16T13:10:30.3448629Z Obtained 25 stack frames.
2023-03-16T13:10:30.3449255Z #0  0x005627dd3e010c in burst_signal_handler(int, siginfo_t*, void*)
2023-03-16T13:10:30.3449948Z game-ci/unity-builder#1  0x007f76129d2980 in funlockfile
2023-03-16T13:10:30.3450599Z game-ci/unity-builder#2  0x005627dd3dc245 in lane_allocator::lane_allocator(ujob_control_t*)
2023-03-16T13:10:30.3451570Z game-ci/unity-builder#3  0x005627dd3dbef1 in ujob_schedule_parallel_for_internal(ujob_control_t*, JobsCallbackFunctions&, void*, WorkStealingRange*, unsigned int, unsigned int, ujob_handle_t const*, int, unsigned char)
2023-03-16T13:10:30.3452576Z game-ci/unity-builder#4  0x005627dd3dd3ca in ujob_schedule_single(ujob_control_t*, void (*)(void*), void*, ujob_handle_t const*, int)
2023-03-16T13:10:30.3453442Z game-ci/unity-builder#5  0x005627dd3da4ff in JobQueue::ScheduleJob(void (*)(void*), void*, JobGroupID, JobQueue::JobQueuePriority)
2023-03-16T13:10:30.3454433Z game-ci/unity-builder#6  0x005627dd3c8d67 in BackgroundJobQueue::ScheduleJobInternal(void (*)(void*), void*, BackgroundJobQueue::JobFence const&, JobQueue::JobQueuePriority)
2023-03-16T13:10:30.3455288Z game-ci/unity-builder#7  0x005627dd0c1a8a in InitialiseBurstDebugDomain()
2023-03-16T13:10:30.3456059Z game-ci/unity-builder#8  0x007f7524dad4e7 in MonoDebuggerHandling::RequestFlushClientDebuggerKnowledge()
2023-03-16T13:10:30.3456900Z game-ci/unity-builder#9  0x007f7524dadb0c in MonoDebuggerHandling::ProcessLibraryMetadata(void*)
2023-03-16T13:10:30.3457563Z game-ci/unity-builder#10 0x00000041c7b3d7 in (Unknown)
2023-03-16T13:10:30.3458104Z game-ci/unity-builder#11 0x00000040517b8a in (Unknown)
2023-03-16T13:10:30.3458627Z game-ci/unity-builder#12 0x00000040507578 in (Unknown)
2023-03-16T13:10:30.3459140Z game-ci/unity-builder#13 0x00000041c69f94 in (Unknown)
2023-03-16T13:10:30.3459651Z game-ci/unity-builder#14 0x00000041c69146 in (Unknown)
2023-03-16T13:10:30.3460148Z game-ci/unity-builder#15 0x00000041c68834 in (Unknown)
2023-03-16T13:10:30.3460710Z game-ci/unity-builder#16 0x007f755045d2d8 in mono_get_runtime_build_info
2023-03-16T13:10:30.3461318Z game-ci/unity-builder#17 0x007f75505fcc0a in mono_runtime_invoke
2023-03-16T13:10:30.3461930Z game-ci/unity-builder#18 0x007f75505fe4c0 in mono_runtime_delegate_invoke
2023-03-16T13:10:30.3462599Z game-ci/unity-builder#19 0x007f755061bec1 in mono_thread_has_sufficient_execution_stack
2023-03-16T13:10:30.3463345Z game-ci/unity-builder#20 0x007f755061bd0a in mono_thread_has_sufficient_execution_stack
2023-03-16T13:10:30.3464145Z game-ci/unity-builder#21 0x007f7550695430 in GC_inner_start_routine
2023-03-16T13:10:30.3464744Z game-ci/unity-builder#22 0x007f75506950c3 in GC_start_routine
2023-03-16T13:10:30.3465311Z game-ci/unity-builder#23 0x007f76129c76db in start_thread
2023-03-16T13:10:30.3465870Z game-ci/unity-builder#24 0x007f76126f061f in clone
2023-03-16T13:10:30.3466410Z Unexpected exit code 139

I guess it is a Unity bug, maybe related to https://issuetracker.unity3d.com/issues/linux-editor-crashes-on-burst-signal-handler-when-universal-rp-camera-is-selected (although this should be fixed long ago).

We just switched to URP ("com.unity.render-pipelines.universal": "14.0.5") and now this issue occurs in the GitHub Actions build.

@achimmihca
Copy link
Author

I only have this issue when building via GitHub Actions. On my local Ubuntu machine, the build works fine.

@AndrewKahr AndrewKahr transferred this issue from game-ci/unity-builder Mar 20, 2023
@AndrewKahr
Copy link
Member

Since you're using unity test runner, I've transferred it to the test runner repo from the builder repo.

@achimmihca
Copy link
Author

By now, we found that the actual build of the project works fine (for Standalone, Android, iOS).
The issue seems to only occur when running the tests for Standalone via GitHub Actions.

@EddieCameron
Copy link

We're seeing this too. Most (but not all!) runs on Github are segfaulting with this same stacktrace when the edit mode tests have completed. Builds and play mode tests are so far completing successfully.
As far as I can tell it only started when we updated from 2022.2.0 to 2022.2.5, which came with updating URP from 14.0.4 to 14.0.6

@simon-icy
Copy link

Any update on this?

I was able to work around the issue by clearing cache and not using a cache step in the unit tests workflow, for future reference, if someone else comes across this.

@timcassell
Copy link
Contributor

I was able to work around the issue by clearing cache and not using a cache step in the unit tests workflow, for future reference, if someone else comes across this.

Thanks for the info. I was able to fix some internal null references (not quite the same error as this issue) by removing the cache step. Unity is weird...

@achimmihca
Copy link
Author

removing the cache step

Did not work for me.

@achimmihca achimmihca mentioned this issue May 30, 2023
Open
@johnfoconnor johnfoconnor mentioned this issue Jul 19, 2023
Open
@crashkonijn
Copy link

I am getting this (all of a sudden, on all of my runs). Unfortunately disabling the cache didn't help. Does anyone have a solution to this? I've already updated to v3, but that didn't help.

@VladTempest
Copy link

Have the same problem, any solutions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@EddieCameron @crashkonijn @achimmihca @AndrewKahr @timcassell @VladTempest @simon-icy