P: Premiere pro crash during scene edit detection

[dj_5891]

• Issue - When I do a scene edit detection Premire Pro crashes everytime time on 25.0 and 25.1
• Adobe Premiere Pro version number:25.0 and 25.1
• Operating system - 
  • Edition Windows 11 Home
    Version 24H2
    Installed on ‎10/‎11/‎2024
    OS build 26100.3476
    Experience Windows Feature Experience Pack 1000.26100.54.0
    
• System Info: CPU, GPU, RAM, HD:

  • CPU: Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz

  • GPU: Nvidia GeForce RTX 3060

  • GPU driver (PC): 572.60

  • RAM: 32 GB

  • Hard Drive: Samsung SSD 870 EVO 1TB

• Video format: 720p 3mb video from youtube 
• Workflow details: Single video clip
• Steps to reproduce - (Very important!) 
  
  • Drag clips into timline
  • Right click and choose scene edit dection
  • Let the process do its thing for a big then after a while it will get hung up and crash
  • (Works fine on previous versions of premire pro
• Expected result - What should have happened after the last step?
  • The software should have went through the process and cut up the clip with edit detection
• Actual result -  Software got hung up and crashed
  
  (mod edit: Primary thread created)

[R Neil Haugen]

Have you tried working with H.264 acceleration turned off in Premiere?

I ask because a recent Windows 11 build has been a right pain for long-GOP workflows.

[dj_5891]

Where is that setting located?

[R Neil Haugen]

In the Preferences ... go through the tabs there, it's in one of them. Might be named differently on Macs & PCs

[dj_5891]

Are you talking about hardware accelration? This is what I see.

[celestial_fashion1111]

Anytime I use scene edit detection in premire pro 25 or 25.1 it crashes my whole computer. I have to constantly swich back to premire pro 24.6.1 for it to work. Was looking to see if Adobe knows about this bug and can fix it since I used this feature everyday for work.

[IanB_360]

Hi @celestial_fashion1111  and welcome to the Premiere Pro Forum community.  Thank you for taking your time to file a bug report. We would like to help figure this out with you. The team just needs a little more information to begin troubleshooting. If you could just jump to the link here  How do I write a bug report and follow the steps to providing more information about your bug, we will gladly take a look.

Thank you 
Ian

[BadGopher]

When analyzing clips for Scene Edit Detection, Premiere Pro 2025 uses all available system memory (ignoring the 'reserved for other applications' preference) and causes the pagefile to grow very large (most recently, from 18 GB to 300+ GB). The analysis process often fails with a "Scene Edit Detection encountered a failure when analyzing the clip." error message.

This issue also exists in the latest beta, but does not occur in Premiere Pro 2024.

Version: 25.1.0 (Build 73), 25.2.0 BETA (Build 104); works in 24.6.4 (Build 3)

System Info:
OS: Windows 11 24H2
CPU: AMD Ryzen 9 7950X
GPU: Nvidia GeForce RTX 4090
GPU driver: 571.96
RAM: 128 GB DDR5
Hard Drive: 4 TB NVMe SSD

Video format: Usually MPEG4 (H.264) in 1080p or 720p. Most recently: MPEG4 Video (H264) 1280x720 50fps 6526kbps [V: English [eng] (h264 high L3.2, yuv420p, 1280x720, 6526 kb/s)]

Workflow details: My primary use case for Scene Edit Detection is to process several hours of video clips (most recently, about 4 hours of video across 3 clips) into bins of subclips while my computer would otherwise sit idle for an extended period. I then assemble the desired video(s) from each bin of subclips.

Steps to reproduce:

1. Launch Premiere Pro 2025 and create a new project
2. Drop video clips from Windows Explorer into the Timeline of the new project
3. Select all clips in the Timeline, right click and select Scene Edit Detection
4. Deselect 'Apply a cut at each detected cut point' and select 'Create bin of subclips from each detected cut point' and then click Analyze
5. Open Windows Task Manager and observe the process for Adobe Premiere Pro consume all available system memory
6. Wait for Scene Edit Detection to fail (or maybe eventually complete)

Expected result:
A) Premiere Pro keeps within a few GB of the configured memory threshold and does not cause the system pagefile to grow by leaps and bounds
B) Scene Edit Detection successfully generates bins of subclips for each clip on the timeline

Actual result:
A) Premiere Pro consumes all available system memory and causes the system pagefile to grow very large
B) The process of analyzing clips for Scene Edit Detection often fails

[Rach McIntire]

Hi @BadGopher,

Thanks so much for your thorough bug report.  We're sorry about the poor experience. Is this happening specifically with longer-duration media or with shorter-duration media as well? Also, just to be sure, do the clips have clear edit points?  Can you provide one of the problem files for us to test with?

Sorry for the frustration, and thanks for reaching out.  I hope we can help you soon.

[BadGopher]

I work with clips that are typically between 20 minutes and 2 hours in duration, and there are clear edit points. I don't have a use case for shorter clips. I am unable to provide one of my videos for testing, but the content is similar to a highly produced on-stage keynote address or maybe a tv news broadcast--steady shots of the presenter cutting between a few cameras and the occasional full-screen graphic or short video.

[Rach McIntire]

Hi @dj_5891,
Thanks for your bug report.  I've merged your post with a few others having the same issue.  Are you able to provide a sample clip for us to test?  When Premiere crashes does it give you a dialogue box to send a crash report?  I hope we can help you soon. 

[dj_5891]

Hi @Rach McIntire 

Yes I can send you a clip if you want to test, where shoud I send it? No it does not give me a dialouge box, it slows down my entire computer then just crashes

[BadGopher]

Ran into this issue again today and instead of dropping back to Premiere Pro 2024, I gave the latest beta 25.3.0 BETA (Build 33) a go and it worked! While scene edit detection was running, I peeked at Windows Task Manager and observed a memory use and release pattern similar to what I see when I use 2024 for this task. Here's hoping a fix lands in a non-beta release of 2025 some day soon.