Search Issue Tracker

Fixed in 2018.1.X

Votes

0

Found in

2017.1.2f1

Issue ID

976554

Regression

No

SpriteToParticles asset crashes editor when selecting game object with Color over Lifetime module enabled

Visual Effects - Legacy

-

To reproduce:
1. Open user's attached project, scene "Effector - Repeler"
2. Enter Play mode or click on "Ranger - Repeler" game object

Expected: editor doesn't crash
Actual: editor crashes when Particle System component has Size over Lifetime module enabled

Reproduced in: 2017.1.2f1, 2017.1.2p1, 2017.1.2p2, 2017.2.0f2, 2017.2.0p1
Note: crash can also be reproduced by deleting all scene objects and executing Undo
Note2: stack trace of the crash:

0x00000001412A9577 (Unity) UpdateTpl<4>
0x00000001412B1A33 (Unity) SizeModule::Update
0x00000001412CD592 (Unity) ParticleSystem::UpdateSizeModules
0x0000000141329AC3 (Unity) ParticleSystem::EmitParticlesExternal
0x00000000539699F3 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.ParticleSystem:Internal_Emit (UnityEngine.ParticleSystem/EmitParams&,int)
0x0000000053969873 (Mono JIT Code) [C:\buildslave\unity\build\artifacts\generated\common\modules\ParticleSystem\ParticleSystemBindings.gen.cs:3958] UnityEngine.ParticleSystem:Emit (UnityEngine.ParticleSystem/EmitParams,int)
0x00000000539680E4 (Mono JIT Code) [C:\Users\Vaidas Macikenas\Downloads\case_976554-TM_Bling\Assets\SpriteParticleEmitter\Core\Code\SpriteToParticles.cs:756] SpriteToParticlesAsset.SpriteToParticles:EmitDynamic (int)
0x00000000539648B7 (Mono JIT Code) [C:\Users\Vaidas Macikenas\Downloads\case_976554-TM_Bling\Assets\SpriteParticleEmitter\Core\Code\SpriteToParticles.cs:329] SpriteToParticlesAsset.SpriteToParticles:Emit (int)
0x00000000539644E6 (Mono JIT Code) [C:\Users\Vaidas Macikenas\Downloads\case_976554-TM_Bling\Assets\SpriteParticleEmitter\Core\Code\SpriteToParticles.cs:308] SpriteToParticlesAsset.SpriteToParticles:Update ()
0x0000000032356F22 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)
0x00007FFE8B125FEB (mono) [c:\buildslave\mono\build\mono\mini\mini.c:4937] mono_jit_runtime_invoke
0x00007FFE8B078765 (mono) [c:\buildslave\mono\build\mono\metadata\object.c:2623] mono_runtime_invoke
0x00000001414143F5 (Unity) scripting_method_invoke
0x000000014140C681 (Unity) ScriptingInvocation::Invoke
0x000000014116497B (Unity) MonoBehaviour::CallMethodIfAvailable
0x000000014117C86F (Unity) MonoBehaviour::CallUpdateMethod
0x0000000140DDC2B6 (Unity) BaseBehaviourManager::CommonUpdate<BehaviourManager>
0x0000000140DDCF4F (Unity) BehaviourManager::Update
0x00000001410C04D3 (Unity) `InitPlayerLoopCallbacks'::`38'::UpdateScriptRunBehaviourUpdateRegistrator::Forward
0x00000001410BE305 (Unity) PlayerLoop
0x000000014010968E (Unity) Application::UpdateScene
0x000000014012D547 (Unity) Application::EnterPlayMode
0x000000014012E677 (Unity) Application::SetIsPlaying
0x0000000140131EE2 (Unity) Application::TickTimer
0x0000000141A945DD (Unity) MainMessageLoop
0x0000000141A95EEE (Unity) WinMain
0x0000000141CF9EAC (Unity) __tmainCRTStartup
0x00007FFEC3DA2774 (KERNEL32) BaseThreadInitThunk
0x00007FFEC45A0D51 (ntdll) RtlUserThreadStart

Also reproducible in release range of 2017.2.0f2 - 2017.2.0p1

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.