reset your preferences -
adobe media encoder: https://forums.adobe.com/thread/1713540
after effects: http://helpx.adobe.com/after-effects/using/preferences.html
muse (mac): https://forums.adobe.com/thread/1246022?tstart=0
if that fails, uninstall, clean (http://www.adobe.com/support/contact/cscleanertool.html) and reinstall
Tried that... it didn't change anything. Program still crashes if i try to preview, work in the library, publish, etc.
there are 4 suggestions there and i'm pretty sure you did NOT do all 4 because the last one takes more than a few minutes.
did you reset your preferences successfully?
did you uninstall?
did you clean?
did you reinstall?
Like I said in my first post, I tried everything I could think of, which included a full re-install with all the steps you mentioned. The only thing i hadn't tried was the preferences in regedit, which was unsuccessful. I'm also now having this issue in MX AND CS5, so I doubt it has anything to do with preferences in one of those applications, especially since I was never able to use CS5 at all...
Are there perhaps some incompatibility issues with certain programs I'm not aware of?
By the way, MX didn't crash *as often* when I was running XP - the issues escalated quite a bit once I moved to Windows 7. Maybe something about 64-bit and flash.exe not working well together??
the next step then requires starting in safe mode, starting flash and testing if all works.
any problems if you do that?
Just got done with work - It still crashes in safe mode.
then you have a conflict with your os and there's probably nothing easy to do to resolve the problem.
Ok... What non-easy things can I do at this point? I'm fairly technically savvy.
3. (Windows) Disable Compatibility Mode.
For information on compatibility mode, see Using Windows 7 or Vista compatibility mode.
Windows Compatibility Mode can cause errors to occur with Adobe Creative Suite products. To disable it, do the following:
- Navigate to C:\Program Files\Adobe\[application name].
- Right-click the product application file and choose Properties.
- In the Compatibility tab, deselect all options under Compatibility Mode, Settings, and Privilege Level.
- Click OK, and relaunch the Adobe Creative Suite 5 product.
4. Disable startup items and services.
- Disable startup items and Services (Windows XP)
- Restart Windows in a modified mode (Windows 7 and Windows Vista)
- Start the system in Safe Boot mode (Mac OS)
5. Log in using a new local administrative user account.
A new local administrative account can rule out network policies, corrupt profiles, and incorrectly setup administrative accounts as the cause of a failed launch. To create a local administrator account, see the following:
- Windows XP: Choose Start > Help And Support and see the article "Add a new user to the computer," or contact your system administrator.
- Windows Vista/Windows 7: Create new local administrator account (Windows Vista) (kb404912)
- Mac OS: Creating and modifying user accounts on the Apple support website. This video demonstrates the procedure to create a Standard user account. To create an Administrator account, select Administrator in the New Accounts menu.
6. Delete all Adobefnt*.lst filesSearch for and delete all copies of the AdobeFnt*.lst file that you find on the hard disk:
(Mac OS) In the Finder, choose File > Find (Command + F).
(Windows XP) In Explorer, click the Search button (Ctrl+F).
(Windows Vista/7) In Explorer, use the search box in the upper right (Ctrl+F).
- Type Adobefnt*.lst and then click the Search icon. If you have more than one hard drive, only search the system (OS) drive.
(Windows XP Search Assistant) Choose All Files and Folders. Under More advanced options select Search System Folders, Search hidden files and folders, and Search subfolders.
- Click within the search results. Choose Edit > Select All, and then drag the selected files to the Trash (Mac OS) or Recycle Bin (Windows).
- (Mac OS) Choose Finder > Empty Trash.
If an Adobefnt*.lst file becomes damaged, it can cause the application to crash, freeze, or quit when you try to start it. Adobefnt.lst files (for example, Adobefnt10.list for InDesign) are font cache files that Adobe applications use to quickly gather and store information about available fonts. If you delete or rename an Adobefnt.lst file, the application re-creates it the next time you start the application.
- Restart the application.
7. Troubleshoot font issues.
Remove or disable nonessential fonts and then restart your Creative Suite application. See:
- Reduce the number of active fonts (Windows XP)
- Reduce the number of active fonts (Windows 7 and Windows Vista)
- Troubleshoot fonts (Mac OS)
8. (Windows) Update your video card driver.Download the latest driver from your video card manufacturer's website or contact the manufacturer for an updated driver.
9. Search the knowledgebase for errors.
Search the Adobe knowledgebase for any errors that appear:
- Type the error into the search field and click Search.
Note: Omit file paths and registry keys from the search string.
10. Run the Adobe Support Advisor.
The Adobe Support Advisor is an AIR app that helps identify and resolve installation issues. It can also assist with errors that occur when AMT is running. For more information, see Using the Adobe Support Advisor (kb405816) and Troubleshoot launch errors using Creative Suite launch logs (cpsid_83478).
11. Perform system troubleshooting steps
Follow the steps in Troubleshoot system errors and freezes | Adobe software on Windows (cpsid_82252) or Troubleshoot system errors and freezes | Adobe software on Mac OS (cpsid_82414).
Hmmm.. I ran across that article earlier. Tried every single step in there, but nothing helped. Advisor doesn't even exist anymore, so not sure how up-to-date that article even is. Also found nothing in the knowledge base. The hardest part is the fact that it never crashes on start-up, so a lot of the troubleshooting steps in Adobe's documentation are useless.
Any other ideas?
I've noticed it crashes much more frequently in my most recent flash project. There are quite a few files in the library (around 1000). Is there an easy way to troubleshoot if a particular library item is causing the issue?
I've been able to pinpoint that my RAM usage skyrockets whenever I do anything in Flash. Once the usage hits the neighborhood of 2GB, the program crashes. This is true of both CS5 and MX. Sooooo.... Now what?
Aaaaaaaand now I can't open any files in MX. Awesome. Not sure what I did... :/
you have a hardware problem, a windows problem or a flash problem.
if it were a flash problem, following the steps in message 1 would have solved the problem.
How much memory is Flash typically able to use before becoming unstable? And is there a maximum file size it can handle? I seriously doubt this is a hardware/windows problem, as Flash is the only program I've ever had issues with. I have the entire CS5 Master Suite as well as a host of other software on this machine, and I've never had any problems except with Flash.
I use this software to edit stop-motion videos and have never found a better alternative. Is there a better program I should be using? I end up with about a thousand 720x480-pixel photos and a couple dozen small sound files typically in each video. Does Adobe have a better solution? MX always did what I needed it to do when it was installed in XP and with smaller files in 7, and I love the ability to edit frame-by-frame with layers and the ability to build flash animations on top of the photos...
if you're only having a problem with a particular flash file you should have stated that.
create a new flash file. is there any problem??
It isn't just this particular file; it typically happens with almost any file I try to edit in CS5. In MX, it seems to happen in proportion to the file size - the larger the file, the more often it crashes. In CS5, it always crashed while in the middle of working on any file - even newer ones - and i've noticed while troubleshooting that the program eventually just freezes when I try to do any memory-heavy operations like publishing, previewing, selecting several items from the Library at once, etc. Any operation that uses more resources. But I can edit a 30,000x30,000 pixel image at 360 dpi in Photoshop CS5 or a edit movies in Premiere CS5 while using Firefox all at the same time with no issues, so likelihood of hardware being the problem is pretty low...
That said, it looks like one of the troubleshooting steps I tried yesterday fixed the crash issue in some of the smaller files I have, but it is still freezing and crashing in all my medium-to-large files. That's why i asked if there were specific limitations around what this application can handle. All the videos I build have at least a thousand files in the library, and I've started to use the Scene functionality a lot more to help break it up, but if I open a larger flash file and select a different scene, Flash crashes. In MX, i can select different scenes without this issue, but it will crash if i try to delete more than one or try to save the file after deleting a scene.
Maybe there's a temp workaround... Is there an easy way i can break up my file into several smaller files without crashing the application? Copying the frames into a new file doesn't copy the library, so i haven't gotten that to work for me yet. Suggestions?
older versions of flash are 32 bit so under normal circumstances only 2gb or ram can be accessed.
Ahhhh, that is a good point. Which versions of Flash CAN handle more? I'm assuming that means CS5 is considered "older"...
flash cc and flash cc 2014 are 64 bit.
And those are available only online, correct? I prefer having a system that's actually installed on my computer vs. a cloud app, so I hadn't looked into those...
Is there a way to limit how much RAM it tries to use so it doesn't crash, or do I just have to find that perfect file size that stays below maximum memory usage? Grasping at straws, i suppose...
cc apps install on your computer.
to initially activate you have to be online (like most adobe programs). to keep using you have to be online, at least, once every 30 to ninety-one days so adobe can check if your subscription is up-to-date.
Ahhh, that's why I didn't do it. I didn't want to pay yearly. I just wanted to pay once and keep the software. I don't update that often and want to be able to get in and use it whenever I feel like it, whether it's now or five years from now (obviously... i still have MX installed! and thank goodness, needed it as a backup since CS5 crashes so much).
Back to my question - is there a particular way you'd recommend going about breaking up these videos to minimize the chance of it crashing? Or is there a way to limit RAM use in CS5?
you can load swfs so no one swf is too large.
I'm not sure I understand what you mean. Is there a way i can save each scene as it's own .swf file?
create a new fla and copy a scene's layers/frames to the new fla.
Thanks! It only took me about 30 crashes and 4 computer restarts to do get them all saved as their own flash files. I had tried doing that in MX and it didn't work because it didn't copy the library over in the old version.
One of the scenes saved down as 111,000 kilobytes. Is that generally large for a flash file? The original file was 286, so now they are between 50k and 111k.
that's large, especially if it's just one scene from a multi-scene project.
otoh, i've had projects that are twice that large because of hundreds of imported bitmaps (and had no problem with crashes).
Yeah, my original file was about 286,000KB, and I'm still having some issues with the 111,000KB scene file. It contains about 345 jpg images and about a dozen small sound files. The sound files are typically between 10 and 50KB.
Oh, well... Hopefully I can get it to work with these smaller files. If it still crashes, I might try to ask for additional troubleshooting ideas.
Thanks again for your help!