Stack overrun error

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?

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.

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

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

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!

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?

Same! Any solutions?

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!

You Saved My Life!

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.