Crash when zooming in

My Illustrator consistently crashes under the following conditions:
outline type
using arrow keys to zoom in
Started doing this a month ago, after this technique working for many years through many versions. Nothing I know of changed at that particular time, except maybe some font changes.
Conditions:
Illustrator CS6 (latest update)
Mac OS 10.9.4
iMac with a Fusion hard drive and 16GB RAM
crashes on pretty many any file, new or old
Troubleshooting we've tried:
-obtained latest Illustrator version (was a couple minor versions behind)
-trashed all Illustrator related preferences (per Adobe's tech article)
-updated FontAgent Pro to the latest (was using FAP5 now 6)
-turned off all fonts except those absolutely necessary
-started Mac in "safe mode" to clear things out
-repaired permissions
-ran Disk Repair (no problems found)
Any ideas what to try next?

Longshot here: do you have Soundflower installed by any chance?
-Jeff

Similar Messages

IPad photo app crashes when zooming into pictures

I have about 15 GB of photos on this iPad- and the photo app crashes any time I try to pinch to zoom into a picture. anyone else having this problem? what's the deal? works sometimes but crashes 2 out of three times.

Did you get any fruitful answers from an Apple Genius? Sure wouldn't mind saving myself a trip. Thanks.
Nutshell:
I've had two iPads thus far where I cannot use the Photos app because anytime I scroll it crashes.
I had my first iPad replaced since it couldn't play any video without the entire machine locking up and requiring a forced restart. (see http://discussions.apple.com/thread.jspa?messageID=11320267&#11320267 ) The Photos app on my first iPad would also crash anytime I attempted to scroll through my photos.
Now, the Photos app on my second, replacement iPad is behaving the same way, it always crashes when I scroll.
Observations:
• I didn't put any of the same photos back on my replacement iPad, I started with an empty Photos app which ever since only contains images that I've saved to the Photos app from other apps on the iPad, e.g. screenshots, saving images from Safari, Mail, etc.
• I did test drive the Photos app after having saved only a handful of images ( ≈ 30 imgs) and was happy to see that it DID NOT crash. Unfortunately it wasn't long after, having had saved a handful or so more images to the photo library that the app again began to crash anytime I would begin scrolling down through images.

Photos app crashes when zooming some photos

Some photos synced from my iMac's iPhoto '11 library are crashing the Photos app on my iPad. The iPad displays these photos are blurry thumbnails, then when I zoom into them, it puts the play button on the photo, like it's a video. If I tap the photo or interact with it to go to the next photo, it will crash the Photos app.
Message was edited by: Evan Wiener

yudashin wrote:
How do you delete the corrupt image files when they can't be opened to delete?
As they were sync'ed in fro iTunes, delete them there and they should then be removes at your next sync

Scribble tool crashes when zooming in

I have rather simple selection to do with PS Touch 1.5.1. I'm using scribble tool and for accuracy I zoom in heavily. After 3 to 4 attempts, I had to give up as some point of time the app crashes fully. Any proposals? Or should I wait for update?
w. Brs,
Rauno

Any general steps to repro? I'm trying to repro but cannot seem to do so. (I'm using PS Touch 1.5.1 on a Google Nexus 7 (2013) with Android 4.3.)
I try to zoom in all the way (400% is the max) and cannot get it to crash.

Captivate course crashes when zooming in on iPad

Hi,
I am having a weird problem and am wondering if anyone else has exprienced something similar. I've published a course as html5 (Captivate7, includes the patch from November), SCORM 1.2.
The course itself, and it's content, plays just fine on the iPad. However, whenever I zoom in, it crashes Safari. I have the course posted to our LMS.
To test if it's the LMS, I've uploaded the course to scormcloud, and it has played fine. However, I noticed, that user zooming seems to be disabled on scormcloud, so I couldn't actually check if it is simply the zooming in, that causes the issue, or if it is my LMS.
Has anyone else experienced this issue, or has anyone figured out a way to avoid this? I know it's possible to disable zooming into websites using meta tags, but am not sure how to make that happen with a file published from Captivate.
Thanks

This worked for me, thanks
dustinrwh
Re: iPad Mini Safari scrolling problem
Jan 1, 2013 11:15 AM (in response to amirfromcupertino)
I was dealing with this same issue an my iPad Mini. Here's what I did yesterday and I haven't seen the problem since:
1) Go to Settings >> Safari
2) Turn on Private Browsing
3) Clear Cookies & Data
I cannot guarantee this will always solve the problem, but it has worked for me.
Let me know if that works for anyone else :)
P.S. I'm a developer myself and I would give the software developers a little slack. Programming is more crazy than people think. Most likely they expected the iPad Mini to work exactly like the full-size iPad, but bugs always pop up. It will get fixed :) Chrome is always an alternative if Safari is struggling.

Acrobat 8 Standard crashes when opening PDFs created from Microsoft Project 2007

Issue: Acrobat 8 Standard crashes when opening PDFs created from Microsoft Project 2007.
OS: Win XP Pro SP3
Error Message(s): None
Details: This issue happens with multiple Microsoft Project files (including new files), multiple PDF creators (included Acrobat 8 Standard) and on multiple computers. We also tried opening the PDFs in Adobe Reader 8 instead of Acrobat Standard 8. There is no record in the event log on the computers of the application crashes.

I may have a resolution now...
I clicked Tools -> Options -> View and turned off Bars and shapes in Gantt views in 3-D" on the advice of someone on a Microsoft Forum. I made three PDFs from three Microsoft Project files (that were having trouble previously) and was not able to get these PDFs to crash when zooming or changing pages. So far so good!
Regards,
Josh Gold
SERA Architects

Photoshop CC crashes repeatedly when zooming

Hey folks, I have been pulling my hair out trying to get Photoshop to stop crashing when I use the zoom tool. It will work fine for the first few zooms, then the next time I zoom Windows 7 will tell me Photoshop CC has stopped working. I have updated to the latest GeForce drivers with no success. Any ideas? I have included basic build info below. Thanks!
Build:
Core-i7 3770k
2 X GTX 580
32 Gb Ram
Lots of Hard Drives

What else have you done for general trouble shooting so far?
Photoshop: Basic Troubleshooting steps to fix most issues
And does turning off »Use Graphics Processor« in the Performance Preferences and restarting Photoshop have any bearing on the issue?

Adobe Photoshop CS4/5 Crashes when using the Move Tool

Hello. I'm here because I'm having an issue with Photoshop.
I was trying out CS5 when it started to crash every time I tried to use the Move Tool. It was the generic error message: "Adobe Photoshop CS4 has stopped working.
A problem has caused Adobe Photoshop CS4 to stop working correctly. Windows will close the program and notify you if a solution is available."
Thinking that it was a CS5 issue, I went back to my copy of CS4, only to find the same thing happening there (I also downgraded because CS5 was also crashing at other random times for some reason, but that's an issue for another time).
This puzzles me because both were working fine before. Granted, I hadn't opened them for a while, but it was a sudden thing.
My first impulse was to uninstall and reinstall CS4. No luck. So then, I uninstalled all third-party plugins, thinking that might be it. Still, the same problem. I started looking around on Google for solutions and found the instructions on resetting the Tool preferences (I chose to reset the preferences for ALL of the tools). When that didn't work, I tried deleting the preferences file outright, which said instructions recommended. Nothing.
I should note that Photoshop crashes when using the Move Tool to move an object without ant lines around it, i.e., a layer. I'll move the object, and after two to three seconds, the mentioned error message will appear and Windows will close Photoshop. This, however, only seems to happen after selecting, copying, and pasting part of a large object with some variation of the Marqee Tool (thus making that part a new layer by default) while working at a zoom of 100%. So, in short, working with a large image like <a href=http://www.wallpaper4me.com/images/wallpapers/ergo_proxy_267_1280-862301.jpeg>This</a> at 100% zoom. The image linked is the image that I was using and am currently using to reproduce the problem. It is 1280x1024 pixels. I have tested this with somewhat smaller, yet comparable images too. Same problem. I have never had this problem working with large images before, and I wonder if anyone has any suggestions short of formatting my hard drive.
The error code, from Event Viewer:
Faulting application name: Photoshop.exe, version: 11.0.2.0, time stamp: 0x4bf2d4f6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x65637275
Faulting process id: 0xe28
Faulting application start time: 0x01cb2bb3471d87bf
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe
Faulting module path: unknown
Report Id: b412e368-97ab-11df-8f49-001d60b646ef
Details:
System
Provider
[ Name]
Application Error
EventID
1000
[ Qualifiers]
0
Level
2
Task
100
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2010-07-25T05:15:57.000000000Z
EventRecordID
78845
Channel
Application
Computer
Gatherum
Security
EventData
Photoshop.exe
11.0.2.0
4bf2d4f6
unknown
0.0.0.0
00000000
c0000005
65637275
e28
01cb2bb3471d87bf
C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe
unknown
b412e368-97ab-11df-8f49-001d60b646ef
Details in XML View:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-07-25T05:15:57.000000000Z" />
<EventRecordID>78845</EventRecordID>
<Channel>Application</Channel>
<Computer>Gatherum</Computer>
<Security />
</System>
- <EventData>
<Data>Photoshop.exe</Data>
<Data>11.0.2.0</Data>
<Data>4bf2d4f6</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>65637275</Data>
<Data>e28</Data>
<Data>01cb2bb3471d87bf</Data>
<Data>C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe</Data>
<Data>unknown</Data>
<Data>b412e368-97ab-11df-8f49-001d60b646ef</Data>
</EventData>
</Event>
System Specifications:
Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7600)
System Manufacturer: HP-Pavilion
System Model: GN697AA-ABA a6214x
Processor: Intel Pentium Dual CPU E2160 @ 1.80 GHz (2 CPUs)
Memory: 2048MB RAM
DirectX Version: DirectX 11
Display Device:
Name: NVIDIA GeForce 8600 GTS
Manufacturer: NVIDIA
DAC Type: Integrated RAMDAC
Approx. Total Memory: 1010 MB
Current Display Mode: 1440 x 900 (32 bit) (60 Hz)
Photoshop Version: CS4 Extended 11.0.2

Even a decent RAM upgrade is usually only a few hundred dollars nowadays, but it's not a trivially simple process. That said, with a little research and care you can do it. Alternatively, you can hire people (e.g., "Geek Squad") to do such an upgrade.
First, you'll need to know what your operating system capacity is. For example, a 32 bit Windows system can really only use up to a bit more than 3 GB of RAM, while a 64 bit Windows system can use all the RAM you can find a place to plug in. What version of Windows are you running?
Then you'll need to determine what RAM you have installed and what your computer's maximum RAM capacity is - usually you can do this through internet research, either by visiting your computer manufacturer's web site or doing google searches. There are even RAM manufacturer web sites that will tell you what kind of RAM your computer needs and suggest sources, for example:
http://www.kingston.com/
It may be that you can just plug additional chips into currently empty sockets, or it is possible you'll need to replace the RAM chips you have installed in your computer to make room for an upgrade. Every computer is different.
If you list your computer model and current RAM that you have installed here, it may be that someone can help with more specific advice.
-Noel

How do I get inDesign to quit crashing when I try to open a damaged document?

Alright, I'm in a bit of a pinch and behind on deadline because of something completely random and out of the blue happening with inDesign. Here's what happened:
I was working on a magazine layout and printed out a PDF draft. The draft looked normal. I saved, shut my computer, walked away, and came back 30 minutes later to find that 9 pages had gone almost completely blank - even the locked layers were gone. I checked the layers and they were still locked. I thought my content had gotten erased somehow. Then I looked again and saw an overseer text symbol in the middle of one of the spreads. I clicked it and was able to enlarge it somewhat. Doing this gave me the spinning color wheel of doom (I have a Mac running off of Maverick now), and every little zoom and mouse movement gave this result that lasted about 3 minutes at a time. I tried saving again (got the spinning color wheel of doom), then shut down inDesign, and tried again. Same thing happened, only this time I got an automatic recovery notice when it opened. Everything else looked normal. I noticed that the content that had been squished was actually also at a skewed angle as well, like it had been rotated at some strange 3D plane. The story board would also expand to 10 times the normal size every time I tried to move the skewed, overset content. I shut everything down again and restarted my computer. Only this time, whenever I tried to open the problematic document, it would give me the auto recovery request, then promptly crash when I clicked "Yes" for auto recover. I tried multiple times now to open the document, thinking maybe I could just wipe those pages and start over again, but it crashes every time.
Nothing like this has ever happened to me before. I have no idea how this happened, and now it seems like I'm going to loose the entire document, about 40 hours of work. As far as I know, nobody else was near my computer in the 30 minutes it took me to shut it and open it back up again.
Help!
Can anybody shed some light onto this situation? Honestly, I'd be happy to just be able to open the document again so I can erase those problem pages and re-do them... I took screen shots of what inDesign was doing before it crashed:
Here you can see that the "P" in the upper left is all twisted, the same way my content is:
This is a zoomed-out image of how big the storyboard would become when I tried to tweak that overset text/ content...

You can try opening the file "as a copy" from the open dialog. You can also try the blind export to .idml: Adobe Community: InDesign 6 is crashing when attempting to open a particular document. All others are opening OK.
and there's a tool for Windows you can try, if you have access to a windows machine: INDDRecovery — a program for restoring corrupted InDesign documents
After that, it's a question of how much money you want to throw at it. Markzware.com has a paid recovery service that will probably work.

Lightroom crashes when rendering Develop preview under Vista 64-bit

I'm running Windows Vista Ultimate 64-bit and Lightroom 1.1 crashes every time I click the "Develop" pane. My images are DNG files without the original RAW embedded.
Lightroom ONLY crashes when I load an image in Develop. If I open Develop without any image selected, it's fine (no image is displayed). I can zoom in to 100% in Library and it works fine. Exporting images to JPG works fine. Editing photos in the Library pane is fine. The crash data is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 1.1.0.0
Application Timestamp: 4677e8e1
Fault Module Name: MFC80U.DLL
Fault Module Version: 8.0.50727.163
Fault Module Timestamp: 4484afec
Exception Code: c0000005
Exception Offset: 0002511c
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
I've uninstalled LR 1.1 and reinstalled and it does the same thing. When I uninstall LR 1.1 and the install LR 1.0 (the previous version) Develop does open, but it doesn't render the images correctly - it looks like it misinterprets the white balance by about 1,500k degrees (very ugly), but Library shows the correct image/white-balance.
I've updated my nVidia 7900 graphics drivers to the latest version, appropriate to my OS and architecture. I've disabled XMP creation and Adobe Photo Downloader, as well as all other running applications (Antivirus, spyware, itunes, etc).
This USED to work fine in Vista and I did not make any significant changes, but I expect it's an issue with WindowsUpdate causing an incompatibility. I can't roll-back to my Vista state when it worked a month ago (that's another Vista frustration).
Anyway advice or comments would be GREATLY appreciated since this is an integral part of my professional workflow. I own a legitimate, licensed copy of both Lightroom and Vista, yet neither company is willing to talk to me unless I pay them money, which I think is complete extortion, but I digress.
Thanks in advance for your help.

Has anyone got a resolution on this? I have the same issue. Lightroom crashes when I click develop and the develop module begins to render the image. Clicking develop with no image selected allows the develop module to load however selecting develop on the menu bar and choosing either previous photo or next photo causes lightroom to crash while rendering an image.
I have a 64 bit capable HP XW8400 workstation with 2 dual core Xeon processors, 4 GB RAM, and a nVidia FX 4400 graphics card. This video card was put in as a test. the original video card was an nVidia quadra NVS something. When I ran the NVS card I used the drivers certified for Adobe CS2. I am running 32 bit Windows XP SP2 with all current updates. I do not have any MS office components installed on this system.
I read of some troubles around the Realtek HD audio driver and some Adobe applications (not Lightroom). Since I have this sound device I disabled it and removed the drivers...still crashes.
I also disabled the Intel VT in the system bios (I believe this is required to run 64 bit XP or Vista)... no change. Also disabled the NX feature...no change.
I also loaded VMware workstation 6.0 and installed Lightroom in a 32bit Windows XP SP2 VM. In the VM Lightroom works perfectly on the same machine...just not as snappy...
This stinks...Lightroom works perfectly on my poky laptop.

Any solution to pixelated images when zooming?

Wondering if there is a solution to prevent pdf images on transparent background from pixelating when zoomed in.
This is a screen capture. There are two knife images. The large white knife is a pdf on a transparent background saved at 108 ppi in photoshop, it is part of a object state/slide show (saved as vector obviously since type is sharp) that fades in. Doesn't seem to matter what size/dimensions I use, it still gets blurry when you pinch and zoom.
See here:
The smaller black knife image at top left is also a pdf on transparent background, saved at 108 ppi in photoshop. It is not an object state,etc.
The knife images look fine at full screen on the iPad, but once you pinch and zoom, both images loose focus and become blurry.
Any solution to this? The images need to be pdf (or png - which I understand will not scale at all), because they are on transparent backgrounds.
Thanks!

Hi gemmie,
Update to latest firefox 15.0 , your system details said you have 14.0.1(because 14.0.1 it is unsupported)
then :
try to [https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_turn-off-hardware-acceleration Turn off hardware acceleration] in Firefox and "disable the hardware acceleration" in the Flash Player too :
http://helpx.adobe.com/flash-player/kb/video-playback-issues.html
http://www.macromedia.com/support/documentation/en/flashplayer/help/help01.html
also try to [http://kb.mozillazine.org/Flash#Disabling_Protected_Mode_in_Flash_11.3 Disabling Protected Mode in Flash] (the link is for 11.3, do the same for 11.4), see the same in "Last resort" in the next link from adobe forum http://forums.adobe.com/thread/1018071?tstart=0
If you still have crashes you must [https://support.mozilla.org/en-US/kb/flash-113-crashes#w_step-2-install-flash-10-3 Install Flash 10.3] but first uninstall your current version with [https://support.mozilla.org/en-US/kb/flash-113-crashes#w_step-1-uninstall-flash adobe uninstaller program] .
It is not so easy, but not so difficult to, you can do it. If you need any help here we are.
thank you

When will Apple resolve the FCPX Crashes when Effects are added to a clip in timeline.

I have tried every route to get answers from Apple regarding system crashes when applying an Effect to a clip in the timeline. I am now getting more aware from posts in all sorts of Forum / Communities that this is causing VERY MANY users a problem.
It would only take 30 seconds for Apple to post a statement to let their users know what they intend or are doing to resolve together with an estimated fix time.
Come on Apple please SAY something at least.
F. Jackson

Here we go - I have another thread that I started the other day, but thought I'd continue this here. I just did an extensive test. Fred, you may be on to something here. I'm beginning to think some of this is only happening if you are:
(a) running the Trial version
(b) Motion is NOT installed
(c) and it may be that the 10.0.1 update has created this problem, although surely Tom and Andy are running that update...
...or some combination of the above. Anyway...
New iMac i5 quad-core 12mb RAM - new machine with total stock config - only Apple software except for Office 2011.
FCP X Trial version, Motion is not installed
I've tried a variety of clips, but to eliminate variables, for this test I just used clips from a Canon 60D. They were imported from the card and converted to ProRes by FCP X.
Again, these crashes only relate to using the Inspector with certain Effects. If the Inspector is closed, I can apply these Effects and they play back flawlessly. However, once I've applied them and selected the clip, clicking the Inspector button causes an immediate Quit of FCP. And, if the Inspector is already open, just applying the Effect to any clip causes an immediate Quit.
These are the Effects that cause the crash (for me) by category:
Blur - Radial, Zoom
Distortion - Earthquake, Fisheye, Fun House, Glass Block, Mirror, Scrape, Water Pane
Keying - Image Mask
Lighting - Highlights, Side Lights, Spot
Looks - amazingly enough, all work except for Glory
Stylize - Censor, Halftone, Line Screen, Photo Recall, Pixellate, Vignette
Tiling - Kaleidoscope, Kaleidotile, Perspective Tile (but strangely just plain "Tile" DOES work)
So, this is approximately half of the supplied Effects. Interestingly, there is not a single category in which ALL of them work, nor one in which NONE of them work. And, by the way, doing this gave me a chance to check out every Effect - wow are there some cool ones I can't wait to work with. And, I got into this routine of highlight clip, make sure Inspector was open, double-click Effect, if no crash just CMD-z and repeat. I threw a lot of changes at it in quick succession and it handled it beautifully, except for the list above.
There is also a third party free effect from Alex4D called Smooth Move. It looks fantastic! It allows Ken Burns-like scaling which somewhat alleviates the weird animation that results if you scale and move at the same time with keyframes, BUT it allows the flexibility to NOT have the move span the entire clip like Ken Burns does. Oops, sorry, that Effect ALSO crashes the Inspector, so I can't access the controls. And, to keep this test pristine, I didn't try the Alex4D Effect on this test iMac, just on my Mac Pro on a clean system install.
Now, if Apple said (or says later) oh, wait, in the Trial version some of the Effects are not adjustable, but they are flawless in the paid version, I'd be fine with that. And, if you guys with the paid version and/or Motion installed say it works fine for you, I believe you :-). It's just that several of us were excited to get the Trial. I've been using FCP since 2003 and LOVE this new version. But, until you figure out that you can't use the Inspector with half of the Effects if you are using the Trial version, it just seems like the thing is unusable and crashes constantly - because it does.
Now that I know this, I don't think I've had a SINGLE crash otherwise - even on my "wrong" install on my MacPro with FCP7 and FCPX both on the boot drive.
David

Crash when second display attached

I'm using Aperture in this configuration:
Aperture 1.1.2
MacBook Pro 15" (with external monitor)
OS X 10.4.7
Aperture is randomly crashing when the second external display is enabled and Aperture is configured to use it. I can crash Aperture fairly easily, although the crashes are random. If the second display is enabled but not being used by Aperture, I do not have crashes.
Questions:
- Has anyone else seen this issue?
- How do I fix it?
Thanks
MacBook Pro Mac OS X (10.4.7)

I am not experiencing crashes, but I am noticing interference on the monitors when Aperture is running using 2 monitor mode. As I move from picture to picture, or zoom in or out of pictures, I see small blue and red squares all over the screen ... as if something was writing to the video buffer. The problem does not manifest itself at any time when Aperture is not running.

Premiere crashes when exceeding ~1.2GB memory usage

This is extremely annoying. I have found Premiere to crash when it hits around 1.2GB to 1.5GB of memory usage on medialayer.dll or something. I was able to crash Premiere in just a matter of seconds after launching it and opening my project. I work quickly, so this happens frequently.
Q9450 Yorkfield Quadcore (12MB Cache), clocked at 3.2GHz
4GB of 1200 RAM
All my scratch disks are set to my second partition, which has around or at least 200GB of free space. My page file is set to about 4GB. My machine is defragmented daily by Diskeeper Pro 2008.
I am dealing with 26 video files and have frame thumbnails displaying in the timeline thing (it makes everything all the more easier for what I am specifically doing) and adds up to around a total of 9 to 10 hours of video and audio. I'm chopping out the intro, credits, and midtro from each video, which is basically what I am doing.
However, I am currently downloading the latest update (which is like 50.3MB) that might possibly fix this issue. At least I hope it does. :( This crash/memory leak is going to drive me insane if it cannot be fixed.
EDIT :: I have observed that every time I save, the memory usage goes up by 200KB to 500KB. For each frame thumbnail that Premiere loads, the memory usage goes up by a whopping 2MB+. This will and does quickly add up for the work I'm doing. Photoshop never unloads any of this memory!
EDIT2 :: By the way, the frame thumbnails are 88x65 sized thumbnails.
EDIT3 :: Even with the latest version and update, Premiere Pro CS3 still crashes for the same reason. I haven't seen the memory usage at 1GB though.
EDIT4 :: Latest updates help though, but does not fix the problem. When I minimize Premiere, usage is 17 MB. When I bring it back up, usage is 32MB. I can keep resetting the usage to 17/32MB simply by just minimizing Premiere and bringing it back up again (and the memory usage reset is about instant). So far I've reset it numerous times when reaching levels of around 600MB to 800MB of memory usage and haven't crashed in my current session due to the memory leak yet.
This seems to be only a temporary solution.
http://www.hlrse.net/Qwerty/premiere-memoryleak-workspace.gif
That is my current workspace. I literally keep task manager open with Premiere highlighted like that so that I can watch the memory usage levels (to know when to 'reset' the memory usage) as I work. Right now all I'm doing is zooming in and out, and splitting videos in two (or multiple pieces).

Q9450 Yorkfield (12MB Cache) @ 3.2GHz
2GB G.Skill PC2-6400 (400MHz) x2 (4GB total, running with 3.5GB due to 32-bit limitations)
NVIDIA FX5200 (temporary, waiting for ATI HD4850 to come back from RMA)
500GB Seagate Barracuda 7200.1 SATA-II w/ SATA-II enabled
I have my 500GB harddrive partitioned into two partitions: 40GB (C) and 425GB (D). C is for Windows XP (includes drivers, codecs, and things that relate heavily to the core of Windows; stuff that isn't important enough to backup). D is for everything else, which includes games, utilities/tools, media (images, video, music), developer material, etc.
On D, you would find the following logical layout of folders:
Developer, Games, Media, Network, Utilities, Mozilla Firefox, Temp.
Temp is so that I can (in an organized fashion) set the temporary locations and scratch disks for programs here. All scratch disks are set to D:\Temp\Premiere, and currently reports 121.9GB of free space. I can easily free up 114GB to 240GB of material on D though (which I plan to do sometime anyway).
What information do you want to know? Be specific, I'm not stupid and illiterate like most people.
EDIT :: I didn't mention this in my post, but I did take the precautions to search through the Troubleshooting database for Premiere, and I did read through the optimizations for Windows XP article (which I already had the same suggestions applied to my computer since the dawn of time -- so that wasn't really useful).
EDIT2 :: I checked the troubleshooting link and none of those really apply. (Do you even know what a memory leak is?)
=P

Crash when scrolling the timeline

this happens every single time:
if I zoom on the timeline, then I scroll to the right (to reveal next edits), Premiere crashes. if I zoom to the left it doesn't crash.
sometimes it says "sorry Premiere has to shut down we'll try to save the project", while other times it simply crashes and the default Apple crash report appears.
this happens on CC 2014.1 and latest 2014.2 and it's very frustrating because I have to use workarounds in order to move through the timeline.
I'm on OS X 10.9.5, on a new Mac Pro with 2x D700 GPUs, 3.5GHz 6 core CPU and 32GB ram.
any idea on what's causing this problem and how to solve it?
thanks!

Here's another thread on a similar if not identical issue: Premiere Pro CC Crashing when Scrolling Through Sequence in Timeline - Audio Waveform Goes Blank First.
In order to keep the discussion centralized, please post the following there:
information about your system
a crash log
If the Renderer is set to use GPU acceleration, please switch to Software-Only [File>Project Settings>General]. Also, if the pulldown menu for the Renderer shows both CUDA and OpenCL, try both of those options.

Crash when zooming in

Similar Messages

Maybe you are looking for