Search Issue Tracker

Fixed in 2018.1.X

Fixed in 2017.4.X

Won't Fix in 2017.2.X



Found in


Issue ID




[Timeline] Timeline with a disabled Audio Source causes Editor Crash when exiting play mode



To reproduce:
1. Open a scene in a project which contains an audio clip
2. Create a timeline
3. Create a Game Object with an Audio Source component and disable it
4. Set the audio clip value for the same Game Object
5. Add the Game Object with the Audio Source to the timeline
6. Play the scene
7. Exit the play mode

Desired outcome: The editor does not crash.
Actual result: The editor crashes.

Reproduced with 2017.1.0b7, 2017.1.0f3, 2017.2.0a1, 2017.2.0b3
Not reproduced with 2017.1.0a1, 2017.1.0b6
Regression introduced in 2017.1.0b7

Stack trace:
(Unity) AudioSource::Stop
(Unity) AudioManager::StopSources
(Unity) PlayerLoopController::ExitPlayMode
(Unity) PlayerLoopController::SetIsPlaying
(Unity) Application::TickTimer
(Unity) MainMessageLoop
(Unity) WinMain
(Unity) __tmainCRTStartup
(KERNEL32) BaseThreadInitThunk
(ntdll) RtlUserThreadStart

Comments (13)

  1. f0ff886f

    Apr 08, 2019 20:21

    This still happens in 2018.3.12f1, and doesn't require a Timeline at all. Just a disabled AudioSource.

  2. JeffSSVR

    Feb 13, 2019 04:34

    2019 folks, I can still reproduce this in both 2018.2.0f2 and 2018.2.20f1. Wish you could reopen a case. I had a crash happening because an object with an audiosource on it fed by a timeline was disabled during runtime. as soon as I moved the audiosource to a part that was not disabled, no more crashing. At least this helped me find a work around.

  3. zoooom

    Nov 27, 2018 16:03

    A variant of this bug is still occuring in Unity 2018.2.11f1 and 2018.2.17f1:

    Receiving unhandled NULL exception
    Obtained 23 stack frames.
    #0 0x000001021ed5ec in AudioSource::GetFilterComponents(std::__1::vector<FMOD::DSP*, std::__1::allocator<FMOD::DSP*> >&, bool) const
    #1 0x000001021ed481 in AudioSource::CleanAudioSource(bool)
    #2 0x000001021c287e in AudioManager::StopSources()
    #3 0x00000101a4f1cf in PlayerLoopController::ExitPlayMode()
    #4 0x00000101a48c5c in PlayerLoopController::SetIsPlaying(bool)
    #5 0x00000101a471ca in Application::TickTimer()
    #6 0x000001006c46ee in -[EditorApplication TickTimer]
    #7 0x007fff52805739 in __NSFireTimer
    #9 0x007fff5069ac87 in __CFRunLoopDoTimer
    #10 0x007fff5069a78a in __CFRunLoopDoTimers
    #11 0x007fff50691d5b in __CFRunLoopRun
    #12 0x007fff50691153 in CFRunLoopRunSpecific
    #13 0x007fff4f97bd96 in RunCurrentEventLoopInMode
    #14 0x007fff4f97ba0f in ReceiveNextEventCommon
    #15 0x007fff4f97b884 in _BlockUntilNextEventMatchingListInModeWithFilter
    #16 0x007fff4dc2ca73 in _DPSNextEvent
    #17 0x007fff4e3c2e34 in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
    #18 0x007fff4dc21885 in -[NSApplication run]
    #19 0x007fff4dbf0a72 in NSApplicationMain
    #20 0x000001006e30f7 in EditorMain(int, char const**)
    #21 0x000001006e3579 in main
    #22 0x007fff784e1015 in start

  4. CakeLegends

    Oct 14, 2018 20:30

    Frankly, it's embarrassing and pathetic that the LTS updates haven't fixed this error, yet because one version of Unity has the bug repaired, they still just mark it off as fixed. As a professional company, Unity3D should be ashamed of themselves.

  5. lingumigeorge

    Sep 20, 2018 11:57

    Similar crash in 2018.2.8f1. Log:

    Receiving unhandled NULL exception
    Obtained 23 stack frames.
    #0 0x000001021e93cc in AudioSource::GetFilterComponents(std::__1::vector<FMOD::DSP*, std::__1::allocator<FMOD::DSP*> >&, bool) const
    #1 0x000001021e9261 in AudioSource::CleanAudioSource(bool)
    #2 0x000001021be65e in AudioManager::StopSources()
    #3 0x00000101a4beaf in PlayerLoopController::ExitPlayMode()
    #4 0x00000101a4593c in PlayerLoopController::SetIsPlaying(bool)
    #5 0x00000101a43eaa in Application::TickTimer()

  6. mptp

    Aug 19, 2018 01:53

    This is not fixed - I have the same issue in 2018.2.0f2...

  7. dri_richard

    Jun 08, 2018 10:28

    Still open in 2017.4.3f1

  8. solarisn

    Apr 30, 2018 01:23

    Getting this crash in 2017.3.1p2 and it's putting a huge wrench in our workflow. I want to upgrade to the LTS stream (2017.4) but it says this was only fixed in 2018.1. Isn't the whole point of LTS that you back port bug fixes like this?

  9. ThroyCZ

    Feb 19, 2018 10:16

    I have same issue with every audio source in timeline but this audio source must be enabled.

  10. AllMightyNico

    Jan 23, 2018 16:33

    Hello, I am working in version 2017.3.0.f3 and still have this issue.

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.