Stack overrun error

[Kirsi21888295ykon]

Since few version ago I've been getting stack overrun errors in Premiere Pro beta. It seems to happen especially when doing something in the Lumetri panel. Premiere seems to work ok, but those errors popup all the time.

Clips are Canon R5/R5C 8K Raw clips in a 4K timeline. ı'm on M1 Mac wiht 64GB of memory.

[Kirsi21888295ykon]

Please comment and investigate Adobe!

[J-TIZZO]

Glad I am not the only one.   Wish there was more info about it

[Grzegorz33760770n990]

Same problem here, please fix it!

[maayanb]

Same problem

[kind_cause0026]

Same problem

[Project27635587akx3]

Same here

[trevor_7307]

Just seen same issue in 25.2.0 build 54

Underpowered M1 Macbook Air. 8GB Ram. 

[tylerm30086065]

112 GB and I get it.

[ingridv64428293]

samee

[gdlkmd]

I've had this issue for quite a while and today found a solution that helped in my case! Turned out the core of the issue was Frame.io V4 comments extension. If you have it installed, try removing it through Adobe Creative Cloud app. Never had the error since!

P.S.
For any Adobe devs reading, FIX THE DAMN THING! Frame V3 was not perfect, but it was WORKING! This thing can't even properly import the comments as markers.

[Amritesh37548832bdwi]

You Saved My Life!

[nrgeorge]

So, I got the same error when working on my 6K BMPCC RAW footage. I fixed it by switching my scratch disc folder to an HDD with more space than my project size. My project is around 3TB. I switched my scratch disc folder to a drive with 6TB of free space, which stopped the Stack Overrun error from popping up. 

Hope this helps!

[Anastasia_Shashkova8941]

Same! Any solutions?

[defaultnb86uebhynct]

I have the same issue but it pops up everytime I Cut or use ''Ripple Trim Next/Previous Edit To Playhead (W and Q)'' Is there a fix? Or someone that can help?

[haley james]

The same thing is happening to me everytime I cut. I even created a new project and assigned a large SSD as the scratch disk. The only extension I have is AutoPod mutlicam editor but it seems like the issue started showing up after I applied "Automatic Click Remover" to the audio. It doesn't seem to interview with working on the project, except that it's annoying. Haven't tried exporting yet.

Thank you to anyone who can help!

[Josh Mulvihill]

Same situatin for me minus the click remover. @Adobe whats up!?

[Carlos285278557xi6]

I am having the same issue! Footage from DJI mini 3 pro and canon R6. 

[ESSTLL3]

Same problem here! Defintely caused by Frame.io : happenned after the 1st time I tried the workflow with seeing the comments directly into premiere with the markers. A the moment it dosen't affect my workflow, but it's annoying to get those alerts constantly.

[ST!LL FR@NK]

Tough day. I gave First Aid to the external disk holding all of my files, and repaired it. Bingo! Except now the Stack Overrun messages are, well, overrunning me. Updated to Premiere Pro 25.2.3 two days ago. Apple M3 Max. 128 GB. Plenty of room on drives for cache. Cleared the cache to no effect. Opened the Frame.io window ( I never use it) - and it is stuck in the endless swirl of contemplation. It does not appear to affect workflow, aside from being super annpoying. Every single action makes a new error message. Even when first opening a project there are 39 Stack Overrun errors like BAM! (sniffle) help?

[Patrick Southern]

ST!LL FR@NK we're having trouble reproducing in 25.2.3. I'd love to catch up with you to try to triage what's happening. Could you email me at psouthern@adobe.com?

[Jake OK]

I'm having "stack overrun" error every time I make a cut.

I don't have frame.io installed. On M3 MAX Macbook Pro with 48GB RAM.

PP25.2.3 (build 4)

[ST!LL FR@NK]

Thank you , @Patrick Southern . It simply STOPPED showing the errors. No idea why. I'm going to let this ride since there is no fix for something that isn't broken tthis week. Sorry for the delay in replay. I have been on the road. THANK YOU!

[Patrick Southern]

Still working with a few of you to triage this issue. Thank you all for escalating with the team.

[Morgan36463395k2yz]

Same issue. Randomly started tonight. 

[Patrick Southern]

Update: We've found the root cause for the stack overrun issue and are working on a fix.