• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Quitting PP 2022 causes Crash on Film Impact "Radial Blur" plug-in effect

Explorer ,
Nov 05, 2021 Nov 05, 2021

Copy link to clipboard

Copied

I saw this listed earlier but it doesn't seem like it was ever resolved. I am getting a hard crash upon quitting Premiere. This consistently happens. Running OS 10.15.7. The specific crash lines are as follows and are always the same--

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

 

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x00000001fdac5000

Exception Note:        EXC_CORPSE_NOTIFY

 

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [95561]

 

VM Regions Near 0x1fdac5000:

    VM_ALLOCATE            00000001fdac4000-00000001fdac5000 [    4K] rw-/rw- SM=PRV  

--> 

    VM_ALLOCATE            00000001fdaf4000-00000001fdaf7000 [   12K] rw-/rwx SM=CO

 

Any ideas or fixes? I read earlier about not running any virus software. I was running ClamXAV. I quit the app but it's still happening.

 

I will note the following: Under Thread 0 I see the following-

 

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

0   libsystem_pthread.dylib       0x00007fff72f26b9b pthread_mutex_trylock + 0

1   com.filmimpact.Impact-Radial-Blur 0x0000000249f2f498 std::__1::__function::__func<C_MemMappedFileLock::Lock(int)::$_0, std::__1::allocator<C_MemMappedFileLock::Lock(int)::$_0>, bool (int)>::operator()(int&&) + 22

2   com.filmimpact.Impact-Radial-Blur 0x0000000249ff7a51 TryCodeInPollingLoop(int, int, float, std::__1::function<bool (int)>) + 75

3   com.filmimpact.Impact-Radial-Blur 0x0000000249f2f38f C_MemMappedFileLock::Lock(int) + 89

4   com.filmimpact.Impact-Radial-Blur 0x000000024a021d25 C_SyncedData::LockSharedMemory(C_Locker&) + 61

5   com.filmimpact.Impact-Radial-Blur 0x000000024a021c0e C_SyncedData::Load(C_DataDeserializer&, bool&) + 62

6   com.filmimpact.Impact-Radial-Blur 0x0000000249fbf25a C_SyncedState::CheckDataSectionReady(int, int, bool, C_SyncedStateUpdateIO*) + 54

7   com.filmimpact.Impact-Radial-Blur 0x0000000249fc99a6 C_SettingsManager::EnsureDataReadyAndLock(C_Locker&) + 102

8   com.filmimpact.Impact-Radial-Blur 0x0000000249fc9a87 C_SettingsManager::GetUser() + 39

9   com.filmimpact.Impact-Radial-Blur 0x0000000249fb3371 C_Analytics::Finalize() + 45

10  com.filmimpact.Impact-Radial-Blur 0x0000000249ffbe7c C_Plugin::~C_Plugin() + 190

11  com.filmimpact.Impact-Radial-Blur 0x0000000249f221b8 C_Plugin_RadialBlur::~C_Plugin_RadialBlur() + 14

12  com.filmimpact.Impact-Radial-Blur 0x0000000249fbde43 C_PluginInstance::~C_PluginInstance() + 23

13  libsystem_c.dylib             0x00007fff72dce13c __cxa_finalize_ranges + 319

14  libsystem_c.dylib             0x00007fff72dce412 exit + 55

15  libdyld.dylib                 0x00007fff72d24cd0 start + 8

 

Does this imply the cause is the FilmImpact plugins?

 

Moderator note: altered your title to reflect issue. Thanks.

TOPICS
Crash , Error or problem

Views

808

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 05, 2021 Nov 05, 2021

Copy link to clipboard

Copied

rlavon,

Sorry! Remove the Film Impact Radial Blur plug-in - that is what is making you crash. Update the plug-in package, it may help. Let us know how it goes.

 

Thanks,
Kevin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 05, 2021 Nov 05, 2021

Copy link to clipboard

Copied

Update-

I upgraded to the latest version of the plugins ( 4.5.5) and it did not solve the problem. The specific plug in type changed from radial blur to blur dissolve, but the Termination Reason was the same.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Nov 05, 2021 Nov 05, 2021

Copy link to clipboard

Copied

Hi Rlavon,

This is Jaap H. Boerhof from the Film Impact development team.

 

Good to know you've already gone ahead and get the latest version of our plugins. 

That's always a good step to start with.

 

Here is what I recommend:

1. Close Premiere & Media Encoder

2. Remove the following folder

~/Library/Caches/com.filmimpact.Plugins

3. Remove the following folder as well:

~/Library/Film Impact/

 

To get the the folders above quickly:
1. Open the Finder
2. Press CMD+SHIFT+G
3. Copy/Paste the folder path 

 

This will create a clean slate for the plugins to work with.

Does this solve your case?

 

If it doesn't, please open a support ticket by contacting our staff support at film impact dot com.

Thank you in advance.

 

Best regards,
Jaap

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Nov 12, 2021 Nov 12, 2021

Copy link to clipboard

Copied

LATEST

Hi Rlavon,

 

Here is a follow-up on this matter.

 

The issue should be solved with the latest 4.5.7 build of our plugins:

Please download the latest version using this link:
https://www.filmimpact.com/download-now/update/?verify=2

 

If you need further assistance, please contact us support at filmimpact dot com.

Thanks you!

 

Best regards,
Jaap H. Boerhof

 

Senior developer at Film Impact Premium Video Transitions

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines