[solved] ver2021.2.* "multithreaded asset garbage collection" thorows invalid argument error

[pivot_RyomaShibata]

I would like to discuss this feature.

Scripting: Multithreaded asset garbage collection and increased speed by up to 2.5x.

Unity 2021.2.0

I reported it as a bug, but Unity doesn’t seem to be responding to it, so I want to discussing it here as well.
Reported issue↓

Title:
[Android, Scripting] The “multithreaded asset garbage collection” thorows invalid argument error

Issue detail:
GC error logs and GC spikes keep occurring when loading a scene or switching the SetActive state of objects, and stopping the entire player activity.

Reproducible in: 2021.2.0 or higher (whitch shipped with “multithreaded asset garbage collection”)
Not reproducible with: 2021.1.*

Logcat output:
03/28 11:59:21.759 1643 1662 Debug v_gal [tid= 1662] gcmONERROR: status=-1(gcvSTATUS_INVALID_ARGUMENT) @ veglDestroySyncKHR(394)
03/28 11:59:22.323 1643 1662 Debug v_gal [tid= 1662] gcmONERROR: status=-1(gcvSTATUS_INVALID_ARGUMENT) @ eglGetSyncAttribKHR(903)

How to reproduce:
1.Update project version 2021.2.0 or higher.
2.Build player with IL2CPP, .NET Framework, ARMv7 setting.
3.Run .apk file with Android device.
Device CPU info:
Processor : AArch64 Processor rev 2 (aarch64)
processor : 0
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2
Hardware : PXA1928

I’ve checked some documentation and it doesn’t seem possible to deactivate “multithreaded asset garbage collection”.
(Maybe this feature is not the cause, but I have to doubt it because it works all fine in 2021.1.* )

Does anyone know any fixes for this issue? or has anyone else faced the same problem?

It could be a problem that doesn’t show up with recent device. But sadly this is my work and I need to fix this problem.

[MartinTilo]

Hello there,
The bug has since been marked as a (potential) duplicate to this issue, which would indicate that it might be related to Addressables?

[pivot_RyomaShibata]

@MartinTilo

Hello there,
The bug has since been marked as a (potential) duplicate to this issue, which would indicate that it might be related to Addressables?

Hi, Thanks for the reply.
I commented out the part of the project that uses Addressables, but it didn’t change the situation.
So, I still think the problem is caused by “multithreaded asset garbage collection” or “Android thread configuration” (both added in 2021LTS).
https://docs.unity3d.com/2021.3/Documentation/Manual/android-thread-configuration.html

[MartinTilo]

Thank you for trying that. Your issue ticket has been reopened but requires more information from you for our QA to be able to reproduce the issue. You should have received an email about this

[pivot_RyomaShibata]

@MartinTilo

Thank you for trying that. Your issue ticket has been reopened but requires more information from you for our QA to be able to reproduce the issue. You should have received an email about this

Thank you so much, I have recieved notify that the issue has been reopened.
And I will send you more info to reproduce this issue in a few days.

[pivot_RyomaShibata]

As we make progress, I will share it in this forum too.

[pivot_RyomaShibata]

[Update]

The problem may be solved!
I think the cause is that we were running a build which is “Optimized Frame Pacing” enabled on a device with an Android API level of 22 or lower.

In other words, Unity is trying to run GC using a API that Android does not support, which is probably causing invalid argument error.

So, maybe Unity should deactivate “Optimized Frame Pacing” option, if “minimum api level” in the player setting is lower than 22.