Search Issue Tracker

Fixed

Fixed in 2020.3.40f1, 2021.3.12f1, 2022.1.23f1, 2022.2.0b10, 2023.1.0a15

Votes

11

Found in

2020.3.37f1

2021.3.8f1

2022.1.12f1

2022.2.0b3

2023.1.0a4

Issue ID

UUM-11191

Regression

No

[Android][IL2CPP] System.Threading.ThreadPool sometimes causes Player to crash when queueing Tasks

--

-

How to reproduce:
1. Open the user’s attached “threadpool-crash” project
2. Build and Run the “SampleScene” Scene on Android device
3. Click the “UniTask.ThreadPool” button when the number increase stops in the Player
4. Repeat the 3rd step 3-6 times

Expected result: Value under the “UniTask.ThreadPool”-named button continues to increase
Actual result: Player crashes in 1 out of 4 builds

Reproducible with: 2020.3.37f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4

Reproduced on: macOS 12.3 (Intel)

Reproducible with devices:
VLNQA00468 - HUAWEI P40 Pro (Global) (ELS-NX9), CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76, OS: 10
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00264 - Samsung Galaxy S10+ (SM-G975F), CPU: Exynos 9 9820, GPU: Mali-G76, OS: 10.0.0

Not reproducible with devices:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12

Crash message:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7b53a00000
x0 0000007b340734c0 x1 0000007b34950c20 x2 0000000000000001 x3 0000007b32a54051
x4 0000007a2b1b0331 x5 0000000000000000 x6 0000000000000001 x7 0000000000000001
x8 0000007b53626bf8 x9 000000000007b280 x10 ffffffffffffffff x11 0000007b3f643598
x12 0000000000000002 x13 0000000000000000 x14 00040d9584cd8400 x15 00003cbc4c94f1d3
x16 0000007b3f6558f0 x17 0000007be20d94bc x18 0000000000000008 x19 0000007b34950c00
x20 0000007b34950c00 x21 0000007b53626c00 x22 0000007b348b6b90 x23 0000007b3f710000
x24 0000007b3f710e78 x25 0000007b53626c00 x26 0000007b34950c00 x27 0000000000000002
x28 0000007b3f710000 x29 0000007a2b1b04b0
sp 0000007a2b1b0360 lr 0000007b3e91318c pc 0000007b3e91504c
backtrace:
#00 pc 000000000039404c /data/app/com.DefaultCompany.IL2CPPThreadPool-m8taik6YPyVqbwyCkV02gw==/lib/arm64/libil2cpp.so (BuildId: dbb1ef319e65bce20fafa5ac345bb5a2a27183d0)
#01 pc 0000000000392188 /data/app/com.DefaultCompany.IL2CPPThreadPool-m8taik6YPyVqbwyCkV02gw==/lib/arm64/libil2cpp.so (BuildId: dbb1ef319e65bce20fafa5ac345bb5a2a27183d0)
#02 pc 000000000035ce8c /data/app/com.DefaultCompany.IL2CPPThreadPool-m8taik6YPyVqbwyCkV02gw==/lib/arm64/libil2cpp.so (BuildId: dbb1ef319e65bce20fafa5ac345bb5a2a27183d0)
#03 pc 00000000003c36b0 /data/app/com.DefaultCompany.IL2CPPThreadPool-m8taik6YPyVqbwyCkV02gw==/lib/arm64/libil2cpp.so (BuildId: dbb1ef319e65bce20fafa5ac345bb5a2a27183d0)
#04 pc 00000000003aeb0c /data/app/com.DefaultCompany.IL2CPPThreadPool-m8taik6YPyVqbwyCkV02gw==/lib/arm64/libil2cpp.so (BuildId: dbb1ef319e65bce20fafa5ac345bb5a2a27183d0)
#05 pc 0000000000091cd0 /system/lib64/libc.so (__pthread_start(void*)+36) (BuildId: 2121a9288a15ea4b9dec0958fdf50848)
#06 pc 0000000000024250 /system/lib64/libc.so (__start_thread+68) (BuildId: 2121a9288a15ea4b9dec0958fdf50848)
at libil2cpp.0x39404c(Native Method)
at libil2cpp.0x392188(Native Method)
at libil2cpp.0x35ce8c(Native Method)
at libil2cpp.0x3c36b0(Native Method)
at libil2cpp.0x3aeb0c(Native Method)
at libc.__pthread_start(void*)(__pthread_start:36)
at libc.__start_thread(__start_thread:68)

  1. Resolution Note (fix version 2023.1.0a15):

    Fixed in 2023.1.0a15

  2. Resolution Note (fix version 2022.2.0b10):

    Fixed in 2022.2.0b10

  3. Resolution Note (fix version 2022.1.23f1):

    Fixed in 2022.1.23f1

  4. Resolution Note (fix version 2021.3.12f1):

    Fixed in 2021.3.12f1

  5. Resolution Note (fix version 2020.3.40f1):

    Fixed in 2020.3.40f1

Log in to vote on this issue

Comments (8)

  1. ssicosm

    Dec 22, 2022 08:17

    Unity 2020.3.43f1 still throws the error.

  2. upr2

    Oct 21, 2022 10:19

    Hi, I wonder when will 2021.3.12f1 be released, too.

  3. ShenDh

    Oct 21, 2022 03:08

    Hi, I wonder when will 2021.3.12f1 be released, too.

  4. tylearymf_unity0001

    Oct 13, 2022 07:41

    Hi, when will 2021.3.12f1 be released?

  5. JoshPeterson

    Oct 10, 2022 11:40

    > I wonder if the problem also happen in versions older than 2021.3.8f1? (2021.3.x)

    Yes, this problem exists in previous Unity versions.

  6. ShenDh

    Oct 07, 2022 06:33

    I wonder if the problem also happen in versions older than 2021.3.8f1? (2021.3.x)

  7. JoshPeterson

    Sep 21, 2022 10:12

    > I cannot see a 2020.3.40f1 version, is it fixed in 2020.3.39f1?

    No, the fix is in 2020.3.40. That release is scheduled to be published September 28.

  8. epernigo

    Sep 20, 2022 16:06

    I cannot see a 2020.3.40f1 version, is it fixed in 2020.3.39f1?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues