Skip to main content
Participating Frequently
September 10, 2025

Audition 2025 crashes when I change the size of the spot healing brush

  • September 10, 2025
  • 5 replies
  • 477 views

I have been having repeated crashes when using the spot healing brush to make an edit in the spectral frequency display. The crash happens when I change the brush size (either using a key command or typing in the number manually). I can temporarily fix the issue by shutting down and restarting my computer, but then it seems to happen again after editing for awhile.

 

Any solutions? I am working on Adobe Audition 2025 v25.3 on iMac (MacOS Sequoia 15.6.1)

5 replies

Participant
October 16, 2025

I and 7 of my students are also having the same problem. Hope the recent update fixes it. I hope adobe decides to look into it even if they can't duplicate the issue. 

Participant
September 24, 2025

I am having the exact same problem. Also on Adobe Audition 2025 v25.3 on iMac (MacOS Sequoia 15.6.1). Everything is fine and if I try to change the size of the spot healing tool, Adobe crashes immediately and does not send a report.

Participant
September 19, 2025

or you can use the brush, but instead of changing its size, just zoom in/out the waveform 😉

ps. the bug is still there

Participating Frequently
September 11, 2025

Thanks Kevin - I am working on a podcast using two .wav files (these were converted from .mp4 files in Adobe Audition). I have it set up in a multitrack, and go in to edit the waveforms when I come across things I need to fix.

For now thankfully I did find a temporary workaround in another thread (here) where another user had this solution: "Until there is a fix with the next update at least I can successfully use the Command-U (Effects > Auto Heal Selection) in Waveform editor to clean up noisy bits." It's not quite as nice as the healing brush, but it works!

 

Thank you for looking into this bug! It's very appreciated.

Kevin-Monahan
Community Manager
Community Manager
September 10, 2025

Hey Becca, 

Thanks for the report. I have not been able to reproduce the error yet. Hopefully, a community member will step up to provide a workaround or some clue as to why this is happening to your particular system. What kind of media are you working with? Let me know. I am sorry for the frustration.

 

Thanks,
Kevin

 

 

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio