Skip to main content
이 주제는 답변이 닫혔습니다.

1 답변

Markeith5EBE작성자
Participant
February 26, 2022

HELLO? PLEASE HELP! I've tried everything that I could find on the threads, but the system keeps shutting down within a few minutes of editing and I've been unable to work. So far I've tried clearing the media cache, switching the Renderer to 'Mercury Playback Engine Software Only', uninstalling and reinstalling Premiere Pro, starting a new project and importing the old one, clearing my Preferences.... is there something I'm missing?

 

Again, here are my system specs and the beginning of the most recent crash report. Please let me know if you need additional information to assist with my issue. 

 

~Markeith

 

System specs: 

 

iMac (Retina 5K, 27-inch, 2020)

Processor: 3.8 GHz 8-Core Intel Core i7

Memory: 72 GB 2667 MHz DDR4

Startup Disk: Macintosh HD

Graphics: AMD Radeon Pro 5500 XT 8 GB

 

---

 

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: Adobe Premiere Pro 2021 [1865]
Path: /Applications/Adobe Premiere Pro 2021/Adobe Premiere Pro 2021.app/Contents/MacOS/Adobe Premiere Pro 2021
Identifier: com.adobe.PremierePro.15
Version: 15.4 (15.4)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-02-26 14:26:13.4538 -0500
OS Version: macOS 12.2.1 (21D62)
Report Version: 12
Bridge OS Version: 6.2 (19P744)
Anonymous UUID: 5534E86C-9F00-49DD-7340-321DB7B7EBB8


Time Awake Since Boot: 4800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Codes: 0x0000000000000001, 0x0000000000000020
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1865]

VM Region Info: 0x20 is not in any region. Bytes before following region: 4294967264
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->

 

Markeith5EBE작성자
Participant
February 26, 2022

Or perhaps it might be related to titles and/or fonts or plug-ins? This began shortly after I added in some end titles. Just realized that. 

 

STILL NEED HELP!

 

~Markeith

Markeith5EBE작성자
Participant
February 27, 2022

Hi Markeith,

Sorry about the crash. It's the weekend and only volunteers are hanging out today, I imagine. Sorry. I would contact support on Monday morning and ask for the video queue if you can't solve the problem by then. 

 

I am no engineer and am an editor like you, but I did isolate the crashed thread, Thread 100. Best clues are in the first few lines of the crashed thread, I found.

 

Before trying troubleshooting steps, though, sync settings to back up all your saved settings. Duplicate the untouched project and place it in your backups folder. If you don't have one, placing the project file in the Auto Save folder is OK for safekeeping. Having a backup at this stage is important, I think.

 

After backing up, trash your media cache from Preferences > Media Cache from the Home screen with all projects closed. Restart the application with the Option key pressed and reset preferences. Are you still crashing? If so, carry on troubleshooting.

 

Looking at the crash report, I do see the expression "TickTime" and from what I know in past versions, that may have to do with iCloud, Dropbox, or some kind of synching service. These can interfere with normal operations. I have discontinued the use of iCloud for my Documents folder for normal operation. See if doing the same on your end makes any sense.

 

Predominant in your crashed thread are audio related terms, like audio renderer, etc. See if you have any third party plug-ins applied to your clips. Preroll is also mentioned, so checking out Preferences > Device Control (where these are controlled) might be worth looking at. I have seen a few editors complain about Device Control > DV causing some issues too. Personally, I can't change the preference to "None."

 

At the top of the crashed thread is: Dispatch queue: com.apple.root.default-qos - which may have something to do with privacy issues, permissions issues, etc. Audio? Privacy? Do you have any automatic transcription going on? Do you live in Illinois?

 

Here is your crashed thread isolated. I'll trim it inline, as well.

Thread 100 Crashed:: Dispatch queue: com.apple.root.default-qos
0 AudioRenderer 0x10df30a21 AR::AudioClipTrackRenderer::Preroll(dvamediatypes::TickTime const&, bool) + 625
1 AudioRenderer 0x10df4ec87 AR::AudioTrackGroupRenderer::Preroll(dvamediatypes::TickTime const&, bool) + 87
2 AudioSupport 0x108947f69 ML::MonitorMixer::PrerollAsync(dvamediatypes::TickTime const&, bool, std::__1::function<void ()>) + 617
3 AudioSupport 0x108954b6b void boost::_bi::list4<boost::_bi::value<dvacore::classref::InterfaceRef<ML::MonitorMixer, ML::IMonitorMixer> >, boost::_bi::value<dvamediatypes::TickTime>, boost::_bi::value<bool>, boost::_bi::value<std::__1::function<void ()> > >::operator()<boost::_mfi::mf3<void, ML::MonitorMixer, dvamediatypes::TickTime const&, bool, std::__1::function<void ()> >, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf3<void, ML::MonitorMixer, dvamediatypes::TickTime const&, bool, std::__1::function<void ()> >&, boost::_bi::list0&, int) + 203
4 AudioSupport 0x1089547da boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf3<void, ML::MonitorMixer, dvamediatypes::TickTime const&, bool, std::__1::function<void ()> >, boost::_bi::list4<boost::_bi::value<dvacore::classref::InterfaceRef<ML::MonitorMixer, ML::IMonitorMixer> >, boost::_bi::value<dvamediatypes::TickTime>, boost::_bi::value<bool>, boost::_bi::value<std::__1::function<void ()> > > >, void>::invoke(boost::detail::function::function_buffer&) + 26
5 dvacore 0x104945bac dvacore::threads::ExecuteTopLevelFunction(boost::function<void ()> const&) + 92
6 dvacore 0x10494595f dvacore::threads::WrapExecuteTopLevelFunction(void*) + 15
7 libdispatch.dylib 0x7ff803305cc9 _dispatch_client_callout + 8
8 libdispatch.dylib 0x7ff8033083bf _dispatch_queue_override_invoke + 801
9 libdispatch.dylib 0x7ff8033153ba _dispatch_root_queue_drain + 343
10 libdispatch.dylib 0x7ff803315b5a _dispatch_worker_thread2 + 160
11 libsystem_pthread.dylib 0x7ff8034b902e _pthread_wqthread + 256
12 libsystem_pthread.dylib 0x7ff8034b7ffb start_wqthread + 15

 

Hope we can help.

 

Thanks,
Kevin


Hi Kevin, 

 

Well, I've done all that you've suggested and the problem persists, with crashes and similar crash thread reports. Thanks for helping me to dwindle it down to something audio related--I'll reach to customer support for the video queue early on Monday to assist in getting to the root of all this. Why did this have to happen when I was so close to finishing! (I've also backed up the project)

 

Here's hoping it gets resolved quickly. 

 

Best,

~Markeith