Steps to reproduce:
1. Open the “IN-116035” project
2. Build and deploy the project on the device
3. Follow the “How to enter the battle scene” video
4. Slide down to Notification Center and back to the Player a few times when battling

Expected result: The Player continues to run
Actual result: The Player freezes or crashes

Reproducible with: 6000.1.16f1, 6000.2.5f1
Not reproducible with: 6000.3.0b3
Could not test with: 6000.0.58f1 (multiple errors in the Console)

Testing environment: macOS 15.6.1 (M4 Pro), macOS 15.6 (M1 Max)
Not reproducible on: No other environment tested

Reproducible with these devices:
VLNQA00623 - iPhone 16 Plus (MXVY3QN/A), CPU: Apple A18 Pro, OS: 18.6.2
VLNQA00626 - iPhone 16 (MYE73QN/A), CPU: Apple A18 Pro, OS: 18.6.2
iPhone 13 Pro Max, OS: 18.7 (by user)

Not reproducible with these devices:
VLNQA00297 - iPhone 11 Pro (MWC62ET/A), CPU: Apple A13 Bionic, GPU: Apple designed, OS: 17.6.1
iOS: 15.5 (by user)

Notes:
- Sometimes it could take ~10 times to slide down to Notification Center for the issue to reproduce
- Possible regression in iOS versions (isn’t reproducible in 17.6.1)
- If the issue doesn’t reproduce, redeploy the project

First few lines of the stacktrace:

{{thread #17, name = 'Job.Worker 0', stop reason = EXC_BAD_ACCESS (code=1, address=0x44)}}
{{ * frame #0: 0x000000010f48e800 UnityFramework`MultiplyVector3 at Matrix4x4.h:289:13 [opt] [inlined]}}
{{ frame #1: 0x000000010f48e7f0 UnityFramework`::Emit() at ParticleSystem.cpp:1022:37 [opt]}}
{{ frame #2: 0x000000010f47f7d4 UnityFramework`::RecordEmit() at ParticleSystemUtils.cpp:164:5 [opt]}}
{{ frame #3: 0x000000010f466b50 UnityFramework`::Update() at SubModule.cpp:117:25 [opt]}}