Crash at project file open

I seem to get this a lot. AE starts up fine. I go to open a project.
And it crashes with some default plug-in error: 'The Plug-In "Glow" caused After Effects to Crash'. And then it saves a recovery file (which is almost always fine to use).
Then the second error is one of two things. "Something something Blitpipe" or "Something something Dynamic Link" (I never use Dynamic Link. Don't get me started!) There's a third type that's recent: "UnconstraintFPSIFApprorpaite. ADBEVideoFPS constraint off etc etc"
If I reopen the original file again and have the Caps Lock activated. It'll load fine. And it won't crash. When I release Caps Lock, the project appears normally without crashing.
Any ideas what the funk is going on? Happening with two machines: Mac Pro (early 2009), 24GB RAM, 10.6.4. and Mac Pro (mid 2010) 32GB RAM, 10.6.4.

I turned OpenGL off, but I'm still getting this error:
I do have some Pixel Bender effects in my plug-in folder, but this project doesn't use any. I will try removing them and see what happens.

Similar Messages

Project files open in read-only mode

project files open in read-only mode in ms project 2013.But in the case of MS Project 2007 it opens in READ\WRITE mode .what should i do so that project will opens in READ\WRITE mode by default in MS Project 2013

In addition to John's excellent reply, I'd add that if you are talking about Project Server, this is by design that the projects in 2013 version open in read-only mode, in order to require an explicit operation to check-out the file. This prevents to have
many checked out files by mistake.
See this
article on my blog.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

G5 Tower Crashes Photoshop on File Open

My G5 2.0ghz DP Tower started closing Photoshop whenever I tried to use File>Open from within Photoshop CS3. I reinstalled PS to no effect. I then reinstalled OSX 10.4.11 and PS to no effect. Files can be opened by double clicking on them with no crash. All other applications still allow File>Open normally. I previously had PS CS2 still installed on my G5 and it too closed on this command. I have since removed PS CS2.

Backup and clone your drives.
Repair them with Disk Warrior 4.
Scan your files for corruption with MicroMat TechTool Pro 4/5.
Format a drive and start from scratch.
A good setup is to have 3-4 drives.
Boot drive for OS and apps
Disable primary scratch on boot and direct it to a dedicated alternate drive #2.
Media drive for projects.
Backups (at least two).
Alsoft Disk Warrior and SuperDuper can help - hopefully you would have picked those up in the past. Preventative maintenance weekly.

Crash destroys project file. Why?

Adobe Premiere Pro CS6
OS 10.7.5, running on a 2.3 GHz Mac Mini with 8GB RAM
I'm learning my way around, transitioning from FCP to Premiere. I've been going into old FCP projects, importing the media files, and re-editing them in Premiere. It's been very helpful!
One of my projects, shot specifically as a classroom challenge, involves the elements for an entire package captured as a single clip. For effective editing, one must go through the mega-clip and make subclips. No big whoop, right? I begin, and get about 1/3 of the way through that process. It's annoying, since there doesn't seem to be a keystroke shortcut for "make subclip." So I look around for a way to try and automate the process.
Now, keep in mind, there's no reason to think it can be automated. There are no start/stop markers in the file, the metadata has been stripped, the timecode is continuous. I set this up deliberately so that FCP's scene detection ability would not work. But this is Premiere, right? I save the file (named "Whylde", and start looking in menus.
"Analyze Content..." in the Clip Menu looks promising. I select my big clip and click that. Media Encoder launches, and Premiere crashes. I send the error report and reopen Premiere.
"Premiere crashed. This may have ruined your project file. We'll try to reopen it, but no promises. If this succeeds, you should save the file with a new name. Do not resave with the same name." I'm paraphrasing, but that's the gist of it. Weird. Ok.
The project opens, and immediately prompts me to save it. I rename it, save it, then take a look. Everything is there, nothing lost. Nothing new, but nothing lost. Well, let's try this again. Clip Menu, Analyze Content... Crash. Error report. Relaunch. "Resave under a different name" warning.
Crap. Ok, moving on, not gonna waste more time on that. But what's with the "don't resave using the same name" deal? I close the copy of the copy and open the original file. It gives me the "resave this with a different name" warning, but this time, I click Cancel. The project opens. Everything seems to be there. I save it. Nothing explodes.
Let's push this, then. Exit Premiere, delete the "Copy" and the "Copy Copy." Double click the original file. Premiere opens, no warning message. And no content. Nothing. No imported media, no subclips.
How is this possible? The file as there, and functioning, moments ago. How can saving it, using the same name, turn a functioning project into an empty project? What would have happened if I had deleted "Whylde" and renamed "Copy of Whylde" or "Copy of Copy of Whylde" to "Whylde"?
And would "Analyze Content..." have done what I hoped it would do?
Mahalo!
Tom G

Analyze Content is chiefly for processing the audio to transcribe speech to searchable/navigable text. You can also have the video analyzed to find faces. Learn more here. In other words, not what you're looking for.
As for the prompt to save a new project on relaunch after a crash, that's simply a measure to give you the best chance of having a functioning project. The original project might be fine, but it could also be corrupted. Best to leave it be and save a copy of the recovered project rather than overwriting the original with the recovered one.
As to the original project being empty, you say nothing of having saved it between the time you imported content and attempted to analyze content. If you didn't save, then it stands to reason that the project would be empty. Note that you might find an auto-backup of the project in the DefaultProjectBackups folder, which is in the same folder as the project file.

SP2013 and Project 2013 - project files open in read-only mode with no options to edit only Save As

Hi all,
Environment:
SharePoint 2013 (15.0.4420.1017) RTM
Windows 8 - Project 2013 (15.0.4433.1506) 32Bit
Issue details:
When opening .mpp files stored within SharePoint they are opened successfully within Project 2013 however they are opened in Read-Only mode with no options to edit/check out only Save As. The
same outcome is experienced if you click the document link within SharePoint or you chose to edit from the document menu.
Opening the file through windows explorer also opens only in read-only mode.
To date we’ve tested the following
Windows 7 – Office 2010 = working as expected
Windows 8 – Office 2010 = working as expected
Windows 7 – Office 2013 = opening as read only, no prompt to edit
Windows 8 – Office 2013 – opening as read only, no prompt to edit
Current thinking is that it is an issue with either the SharePoint Office Documents Class ActiveX control or Project 2013 itself interacting with SharePoint 2013.
We have tested this in multiple SP2013 environments with the same outcomes.
The workaround therefore is to save locally and then upload again which is not ideal.
Unable to find an exact issue match to this.
Any help with this appreciated.

Hi Dan,
For us after investigating this further it was found that using the document menu to edit or checkout and then edit results in the project file being opened in read-only mode.
The same issue was present for Visio files.
Using the FILES ribbon menu results in the document being opened in edit mode successfully in both Project and Visio.
Please note that we found that this issue only exists within document libraries where checkout is required to edit which was our case. If checkout is not required the document
menu can also be used as expected.
Cheers,
Dan

PS CS5.1 crashes when using file open but not with bridge or "open as smart object"

I'm using a Mac with Snow Leopard and Photoshop CS5.1 Extended
When i try to open a file largen than ~50MB with double click in finder or with file>open in PS, the program loads the psd and shows it, then 2-3 seconds later PS crashes. If the psd is under ~50MB everything is fine.
If i open it with file>open as smart object or via the mini bridge, everything is fine, and i can work with it.
How can this be fixed?

Make sure you submit your crash report as it helps us track and resolve code for crashing issues.
Submitting Crash Reports: http://adobe.ly/gNJWVY
If you post one of you crash reports here?
Location of Crash Reports:
Users/<your user name>/Library/Logs/CrashReporter

My project file opens up in an empty file, where are my clips titles sound effects that were there? premiere pro cc

i had dozens of clips, a few titles and a couple mp3 files..... the timeline layers are there, with no files, and my project file is empty......
all of my media sources are connected to the computer.....
will i need to start over?
I am using a 30 day free premiere pro cc download, it that the problem? I am connected to the internet.....

Hi,
As long as you saved the changes in your project, you should be able to see it there. A few times i have seen a similar issue happen where Premiere would not open the sequence you were working on the last time. Make sure you have the right sequence open. You can search for the right sequence in the Project Bin.
Using the trial version is not the problem.
Thanks,
Rameez

LabVIEW 2012 crashes on different File Open/Save dialogs, if last working directory no longer exists

On several Windows 7, 64 bit machines, if I open LV2012 SP1 f1 64 bits, create a VI and save it on a directory, exit LabVIEW, delete the directory where I saved the VI, restart LabVIEW and do a File/Open, LabView goes puff and disappears.
Sometimes it happens on File/Save As. To fix this I have to double click on an existing VI on Explorer, save it, and then after exiting and restarting LabVIEW I can do File Open again.
I do have Classic Shell installed on all the systems, but even after uninstalling it and rebooting the machine, the behavior is the same.
I tried removing the file from the list of last opened files in LabVIEW.ini but that doesn't do the trick.

Not sure if this is related or something else, however I now have a VI on my desktop that if I double click on it brings up LV 12.0.1f3/64, which opens and shows me the file. If I then do File/Save As/Rename and hit Continue, LV crashes.
Error is: Exception: Access violation (0xC0000005) at EIP=0x000007FEFC2DE3C4. I have an about 200 KB dump file if anyone wants it, as the Send button on my error report is disabled and help just tells me to contact my administrator, which is me (and I configured the VLM to allow users to do that, stop and restarted the VLM but still no go).
Lvlog.txt is
#Date: Wed, Aug 21, 2013 3:27:32 PM
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 12.0.1f3 64-bit
#AppKind: FDS
#AppModDate: 05/29/2013 21:55 GMT
#LabVIEW Base Address: 0x0000000140000000
<DEBUG_OUTPUT>
8/21/2013 3:27:41.720 PM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 71bcb82e-95ba-41ca-884d-efe3b7fc1779
ExceptionCode: 0xC0000005�r
</DEBUG_OUTPUT>
0x0000000141DBE41B - LabVIEW <unknown> + 0
0x0000000141DBEA62 - LabVIEW <unknown> + 0
0x0000000019C47D1B - <unknown> <unknown> + 0
0x000000000293A7E0 - <unknown> <unknown> + 0
0x0000000000424FB0 - <unknown> <unknown> + 0
0x0000000001000000 - <unknown> <unknown> + 0
0x000000000000000F - <unknown> <unknown> + 0

Noninteractive project file opening in Director

Hi, folks!
I wonder if it's possible to write an xtra plugin which would
open some Director project file while closing the current one?
I'm making a fully automated Director project publishing
process using Ant and need some way to open the project file in the
existing instance of Director. One possible way to go is to launch
the Director before publishing via command line passing the path to
the project file as an argument. The downside is speed - it takes
about 10 seconds for the new Director to launch and getting a bit
frustrating to wait so much during active development cycle.
Thus I'd like to use following algorithm:
1) If Director is not opened open it via command line and
pass the project file, go to 3)
2) If Director is already opened close the current project
file and open the required one, go to 3)
3) Publish the project file
Is it possible at all?
Thanks in advance.

Hi Raveen,
Does it happen :
for all project files or just 1 unique file?
for all users or just you?
on different machines or just your machine?
with all browser (chrome, mozilla) or just IE?
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

FCP6 Project Files Open in FCP7?

Hello
Just wondering if FCP6 project files, (created in a G5 desktop 10.4), will open in FCP7 in a Mac Pro with Lyon or Mt. Lyon? Then saved as a NEW/different file as a FCP7 project file?
Thanx
Mike

Yes. They open fine. FCP 7 will just update the project file

Final Cut Pro HD project file opens slowly

I have a very large movie project which is connected to about 800 gigs of HD footage split between two Lacie Extreme hard drives. Everything used to open fine, but when I tried to open the project this week, final cut opens fine but then it gets to the "reading project" and it takes an hour just to get to one percent. It did open after 30 hours or so.
I brought my hard drives to a computer lab and the project opened there, although the computer soon ran out of memory. My project files aren't corrupted, and my hard drives seem to be fine...so why is it taking so long for the project to open on my computer?
I've also had trouble copying files from my hard drives to my computer and vice versa. The larger the file, the longer the copying stays at "0%, 1 minute remaining" until it finally starts copying, at which point it is normal. Could this be related?

Thanks for responding.
I found that if I set final cut to play the footage at lower resolution and half the frame rate, the sequences would play without freezing as much, but this doesn't solve the bigger problem.
I have Activity Monitor open and right now it says Final Cut is using 8.4% CPU, with 654.2 MB of Real Memory and 1.76GB of Virtual memory. When I go to "Inspect" and to the Statistics tab, is says "Page Ins: 58398" There are also stats about Shared and Private Memory. I don't know how to interpret any of this.
I don't know that I have CMYK graphics, and what is multi-clip?
My hard drives are 80% and 95% full.
I will try duplicating the project and deleting all but the current version of my sequences. I will also try to use render manager. Are you saying it might help if I delete all renders and rerender what I need?
I did copy one sequence into a new project and am trying to open that now. It is taking a very long time...it will certainly load must faster than the huge project but it doesn't seem to have solved the problem.
Let me know what you think & thanks.

Photoshop crashes with 1 file open and opening second from Desktop

I have an odd dilemma: a user can work on a single file fine in Photoshop. If she tries to open a second file in Photoshop and chooses 'Desktop', Photoshop immediately crashes/closes.
I logged into the computer as myself with Administrative privileges and was able to do the above without Photoshop crashing. I logged into the computer under a different general account with the same privileges as the user and was again able to do the above without Photoshop crashing. It appears to be something related to her profile, but a profile rebuild did not resolve the issue.
I read somewhere else on the forums about choosing a local printer. I did that, but the problem persisted. Are there any other user-specific settings that may be causing Photoshop to crash?

We ended up having to rebuild her entire computer image from scratch. That seemed to resolve the issue (albeit a time-consuming process).

TextEdit under SnowLeopard crashes reliably during File- Open

I just upgraded to SnowLeopard. Until this morning, TextEdit worked fine. Now, I try to edit a text file, bring up the Open dialog, navigate to the directory containing the file, and before I can select the file, TextEdit crashes. It does it every time. Each time it sends some info off to Apple.
I need to edit some files. What's the problem?

Does it only happen when trying to open files from a particular folder?
Or does it happen no matter which folder you navigate to?
(I'm thinking there's a corrupted file of some sort in that particular folder.)
charlie

Warp stabilizer is crashing my project upon open. What do I do?!

Hi guys,
I'm guessing the best thing that I need to do is remove the plugin temporarily from my adobe location, but I can't seem to find it. Anyone have any suggestions on how to remove it or even how to deal with this problem? This is on CS5.5, but from what I've read of WS so far on these forums is that it's causing problems all over the place... (from now on, I will do warp stabilizer and export that clip separately from the project for the final product...)
Thanks!

Wow. Nevermind. I answered my own problem. I was searching for something with the word "Warp" through my files and never tried "Stabilizer"... For those of you wondering, although Premiere realized that WS was absent, it successfully opened my project.

Tiger: crashes when using File Open dialog to explore file server

We have a new Intel-based iMac running Tiger.
It connects to our file servers just fine when using the desktop/finder. But when in Quark 6.5, or Acrobat Distiller, doing anything that results in the "browse" files dialog messes up when trying to access one of our file servers.
Occasionally, it will "unexpectedly quit" the second I click on of the shares listed in the left-hand box of the dialog. Sometimes you can look around, but when scrolling up and down in the panes, the list gets graphically messed up, or simply doesn't update properly. Actually clucking on a file results in the program Not Responding + Beachball. Trying to cancel the browse box also results in this.
Frustrating. Any tips?
iMac 2Ghz Core Duo Mac OS X (10.4.7)

I think I got it licked: turning off IPv6 at the client resulted in the problems going away (not extensively tested this, though).
Viewing the AFP logs on the file servers being used showed connections logged as IPv6 instead of IP. I thought this a little odd, as we have Tiger throughout, and IPv6 left at the default "automatic" on all, and they all showed up in the logs with their standard v4 IP address.
I would be interested in an explanation of why this might have affected it. Right now, I'm a little miffed that such an unnecessary (to most) complexity-creating feature is on by default.

Crash at project file open

Similar Messages

Maybe you are looking for