Participant

Question

Premiere Pro CC Crashes when changing to certain workspace layouts

Forum|Forum|8 years ago
March 28, 2018
10 replies
11572 views

When I try to switch to "Assembly" workspace, the entire interface stops responding and I can't do anything until I force quit.

I'm using a MacBook Pro (15-inch, 2016), 2.9 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 460 4096 MB Intel HD Graphics 530 1536 MB

This topic has been closed for replies.

Jon.M.

Inspiring

Well, it's a few years later and I am having the exact same problem. Switching to standard Color workspace works fine. My custom user Color workspace with Scopes, crashes my desktop pc every time I select it. I seem to see a "ram" notice flash occasionally when crashing. Haven't tried CC Cleaner yet, did uninstall and re-in.

Didn't seem to happen on the previous version. currently on PP 14.7.0 build 23

I Will report back when I discover anything in the event someone is having similar issues.

Intel Core 10920X 350GHz trubo'd 37%

64gb ram

GTX 1080ti

3 SSDs

Media raid

Jeff Bellune

Legend

Try deleting your custom color workspace, then re-create it.

dev_willis

Inspiring

I also have this problem and am going to try the troubleshooting steps listed above. It's definitely frustrating but you have to understand that this software is free and open source, developed by a community of volunteers who do it in their free time. So you can't blame them for not having the quality control resources of one of the world's most profitable corporations.

jimbo_hippo

Inspiring

That's interesting Anthony. You seem to have got one step further than me with this. I have found that switching to 'Color' or my custom layout 'colour with Monitor' is usually what crashes my PP on my MacBook Pro. Since I usually have lumetri scopes open in both those layouts, this could be useful info. I shall play around with this theory and see if I can add any weight.

In the meantime, I shall continue working on my project entitled 'copy of a copy of a copy of a copy of...... '

E

Erikb4123

Participant

I definitely realized that if I go from my Custom Editing workspace to the default Color workspace to my Custom Coloring workspace it won't crash. And then from the Custom Coloring workspace I have to go back to the default Color workspace back to my Custom Editing workspace.

Now that I know that, it's really just an annoyance, but not the end of the world. I've actually been experiencing this for about a year but nobody at Adobe seems to care. The updates haven't helped.

R Neil Haugen

Legend

This stupidly annoying behavior is ... stupidly annoying.

Please file this on the bug/feature UserVoice system which feeds right into the engineer's system so they know it's happening. Adobe is very metric-driven. That adds metrics which means better chance of budgeted time to run it down.

After filing, post a link back here so anyone else looking this up with the same problem can upvote it. More metrics is more better ...

And I've presumed you've already tried "Reset to saved layouts" and trashing preferences to fix this.

Neil

Adobe UserVoice Bug /Feature form: https://adobe-video.uservoice.com/forums/911233-premiere-pro

Everyone's mileage always varies ...

A

aBolt

Participating Frequently

As far as I can troubleshoot, the problem is with the lumetri scopes window. I have created a workspace with everything but the lumetri scopes window available and I don't seem to have any trouble switching from one workspace to another, to color or away from it when the lumetri scopes window is not open. Then when I go to my old workspace with lumetri open it can crash (THOUGH NOT ALWAYS?!) - it's really frustrating to not know why it's crashing. But near as I can tell it has something to do with lumetri color scopes.

Further investigation. I could not get the program to crash with lumetri scopes not on screen. Then I went to window > lumetri scopes... no problems. Then I tried to divide a window to half the space each of the windows shared on my screen (they would not be tabbed together, but side by side at the same time - when you drag a window to the edge of another and the edge trapezoid appears, apologies i don't know the technical term here). THATS when it crashed. This behavior is present if you drag to the left, top. Interestingly both the bottom and right trapezoids will fail but not the first time... I have to load the window, put it to the right, it will load usually, then if I close the window, or reset to saved work space then try again it will fail on the second time..

During this I also noticed that, you would drag the scopes tab to the trapezoid, then it would hang, then if you force quit the program it would pop up saying you were force quitting it cause it was broken or what ever, then RIGHT before the screen would close if you press the okay button fast enough, the scopes window would go to where you put it, then the app would close. So some process is hanging, that is getting quit before the window movement can be finished. Then in quitting it, the window can finish updating, then the program overrides it and quits.

Finally in just closing and opening the lumtri scopes panel, panel > close panel, Window > lumetri scopes (and repeat) I have noticed that eventually it will crash, though I can't always predict when it will.

EDIT: I have found this behavior is consistent regardless of what workspace you are in. I can repeat this behavior in the color workspace, custom workspaces, or any other workspace. Lastly this behavior can be replicated with as few panels open as the program monitor, lumetri scopes, and the timeline.

Does this illuminate any underlying issues for anyone more knowledgeable than I?

macOS High Sierra

iMac late 2013, 21.5"

2.7 GHz Intel Core i5

16 GB 1600 MHz DDR3

Intel Iris Pro 1536 MB

PP 12.1.2 (69)

Video of the problem here (I cover up the top bar where my personal information is, but all that you miss me doing is selecting the window tab in the application menu bar).

Jeff Bugbee

Community Expert

Please see this listen of Known Issues in the latest release:

Known issues in Premiere Pro version 12.1.2

Crashes
Switching workspaces can lead to Premiere Pro not responding or crashing.

Carson Jones

Known Participant

Thanks for the info Jeff. Wondering why they haven't released a hotfix for this. Seems like a major feature that would / could affect all users. This is the first time I've used PPro in some time and for me to stumble across it almost immediately... well lets just say that if I had to use the app everyday in production I'd be screaming at Adobe to fix it asap.

Out of curiosity if users downgrade to the previous version is the bug there as well?

R Neil Haugen

Legend

You won the lottery on this one. Most of us aren't having any crashing on changing workspaces, which is probably why it's being a bugaboo to fix. You can't fix what you can't replicate, or at least get some data as to what's going on. For those with crashing due to workspaces, the most seem to be color, followed by a close pairing of audio & graphics. Assembly is even more rare.

The 12.1.2 release is by far the most stable one they've had in as long as I can remember. The number of posts on here dropped after that release, and the normal thing is for the posts to jump for a while after a release. So I'll give the management credit for that. BTW, the program development manager for PrPro changed just over a year ago, and I've been pleased with most of the decisions since. I wouldn't expect to be pleased with all, being rather opinionated and ... well ... unique in viewpoint.

I also use Resolve at times, and ... have become quite familiar with this forum's analogue over 'there'. No software of this complexity seems perfect. But naturally, I want what I use the most to simply work as expected, as does everyone. So yea, stability is a huge thing.

Love the way you can set an area or whole frame and Resolve matches the 'brightness' throughout a clip to that frame, two different effects to do that. Wish PrPro had it ...

Neil

Everyone's mileage always varies ...

Carson Jones

Known Participant

I'm seeing this as well. I've completely uninstalled PPro and wiped prefs / rebooted / installed / rebooted / opened... created new layouts and boom... crashing again.

This is making PPro pretty much useless.

Workstation specs...

i75960x

64 GB memory

3x GTX 1080 (Nvidia driver 398.82)

Windows 10 Pro (64bit)(1709)

R Neil Haugen

Legend

Did you uninstall with the Adobe CC Cleaner Tool, or just from the CC app?

Neil

Everyone's mileage always varies ...

Carson Jones

Known Participant

Didn't use the CC Cleaner Tool. Frankly I use Resolve 98% of the time but had to grade in PP for this one particular project I'm on. I simply stayed in the custom layout (dual display grading setup) and things were stable enough. I've no time to troubleshoot this I'm afraid.

This is the kind of buggy troubleshooting I've come to expect from Adobe. Hoping that they start making things more stable / reliable instead of worrying about features. Let's get the apps stable and then focus on features (my opinion).

Semihawk

Participating Frequently

I have the same issue. Especially switching to the color workspace, adobe crashes with no error message.

I tried the steps outlined above including cleaning and reinstalling premiere

intel i7 7700k

32GB ram

geforce 1070ti

windows 10

R Neil Haugen

Legend

Please post on the UserVoice system they have listed on the Overview page of this forum. That has been fixed with the 12.1.2 release for the vast majority of users, and they're trying to nail down what is happening on the systems still showing this.

Neil

Everyone's mileage always varies ...

Semihawk

Participating Frequently

Thanks Neil. I'm on

Creative Cloud Version 4.6.0.384

Premiere CC Version 12.12 build 69

omercengel

Participant

The workspaces are great, but they should not cause so many problems. I want to change a workspace according to my needs, but every time I do that, the system crashes after a while, and I need to reset to saved Layout. Adobe should find a solution for that.

R Neil Haugen

Legend

This isn't a particularly common problem, but a very annoying one nonetheless if you have the problem.

For recurring workspaces issues, the only answer I've found is to download/run the Adobe CC Cleaner tool, and unlike the formal instructions, use that to both uninstall and clean up the extraneous files left around by the CC apps. Reboot, download a fresh copy of the app, and see if it works. Might take a couple goes at it.

Neil

Adobe CC Cleaner Tool: https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

Everyone's mileage always varies ...

M

marketings13046203

Participant

I have been having this same problem as well. When I switch to the "Color" workspace, the application freezes and within 15 seconds a prompt comes up saying that the program has stopped working. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

My computer:

Intel Core i5-4570 CPU @ 3.20 GHz

16 GB RAM

64-bit Windows 8.1

NVIDIA GeForce GTX 760 2GB

S

sheilab17413429

Participant

I'm having this very same issue and it just started happening on 4-17-2018 (yesterday as of the writing of this post). I have never had PP crash in this manner. Please advise.....

R Neil Haugen

Legend

The answer is in a post above.

Neil

Everyone's mileage always varies ...

R Neil Haugen

Legend

Go into the Window/Workspaces menu and select "Reset to saved layout" ... and you may need a second or third 'application'.

Neil

Everyone's mileage always varies ...

anthonyc78954971

Participant

I don't know why this worked, but it did. VERY, VERY Random. Helpful, thanks

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded