Aperture hangs / crashes

Staring to want to use aperture properly, I decided I put the library files on an external harddisk. I think this is when the problems started. I tried to import pictures from my Canon5D (using USB, 8GB CF ExtremeIII in camera, half full)
It crashed - I suspected connection to the external (WD Passport). esed different HDs then went internal, then copied the CF card to the desktop ... at this stage (import from desktop to libraryfile on local HD) it sort of worked, but then locked up on creating thumbnails.
many restarts later, it looked it worked, only to lock up again. Firefox crashes now too.
Aperture 2.1 and OSX 10.5.4 ... could 10.5.4 be the culprit?

All kinds of things affect overall operational speed and stability with heavy graphics apps. It sounds like an OS/installation issue. You did not recently (not recommended) "migrate" an OS installation did you? Migrating from Tiger to Leopard in particular is known to be problematic.
Make sure that the OS and Aperture are both at their most current versions.
Although repairing Permissions is not a fix for poor performance, many of us on the PS forums, for instance, find that religiously repairing Permissions immediately before and immediately after every installation of any kind helps keep a graphics box running more smoothly. Similarly, avoiding letting games or crapware (e.g. any free non-Apple app) get anywhere near the box also helps.
Good luck!
-Allen Wicks

Similar Messages

Aperture Hangs / Crashes on Import

Hi,
When I drag images from the finder to aperture it now crashes - I then have to force quit and restart and the images are there. This only started happening recently.
I've tried updating to the latest OS and 2.1.1 Aperture and also reinstalling but no joy. Any ideas??
Thanks,
Kerry

Check out this thread: http://discussions.apple.com/thread.jspa?messageID=8197313

I get hangs using plug-ins (NIK), and can't export (hangs/crashes). Anyone experiencing this?

Updated Aperture today (3.4.3) running 10.8.2. Now I get hangs using plug-ins (NIK), and can't export (hangs/crashes). Anyone experiencing this?

Andrew,
In general, I've found the Nik plug-ins to be the least problematic of all that I use. Unfortunately you haven't provided enough information so that help can be focused on your problem. So here are some of the standard steps to take.
1. Make sure you are running Nik's latest versions. There were earlier ones that didn't work properly with ML.
2. Which plug-ings are the problem?
3. Have you tried the repair/rebuild option on your Aperture database? Often what appears to be problems with a 3rd party item actually stem from some sort of fault in the database.
4. If you're really stuck do the following steps: A. Delete the Nik plug-ings. B. Repair/rebuild the database. C. Download Nik's latest versions. D. Reinstall. E. Test.
This is a generic problem solving approach that fixes many things. Also, you should examine if it is a particularly type of file or set of photos or something specific in the images you are working on. A corrupt image, for example, can produce really weird things on occasion.
Hopefully some of this is useful. If not, more detail is needed.
Robert

Aperture hangs on imports and other stability issues

My aperture will hang on imports, does not like me to do anything else at all when importing, lest it hang and if it hangs once and I force quit I have to restart the system to make it work again. I have had 5 crashes today and really PO'd. This is 1.5.6 and I am running 10.5.5.

Have you done anything to the files before importing them? In particular I'm thinking about giving them keywords through Bridge or LightRoom?
I have experienced Aperture hanging until force quit if I had done keywording to the (in my case) DNG's via Bridge / LightRoom prior to importing them into Aperture.
Regards
Paul K

Aperture Hanging in Books

I upgraded to Leopard a few weeks ago and was using Time Machine and included Aperture backups while Aperture was running. I've since read that there's a problem with this, so I stopped Time Machine backups of my Aperture Library.
But now, every time I try to edit text on a page of a book, Aperture hangs. If I type 25 characters, for example, it will lag behind... showing one character every 5 MINUTES or so until it catches up with my typing... which would take about two hours for the 25 characters. I have to force quit. I've tried restarting and repairing permissions. No help.
Do I have a corrupt library? If so, what do I do? I have 3 vaults, all created in the last day or two.

Delete Aperture, open App Store > Purchases and download Aperture. This should fix your issue

PS CC (since JAN 2014 update) Layer-mask editing causes hangs/crashes

ONLY since JAN 2014 update, PS CC has been hanging/crashing when I paint/edit a layer mask. All may be well at first (or not), but suddenly the display of the mask (or mask overlay on the layer itself, as shown when hitting backslash key) is not shown in full but renders in s-l-o-w-l-y in rectilinear pieces <snapshot below was taken before video card upgraded but is still typical of what I mean>. When I view Windows' Task Manager for PS, I see my CPUs are each working at their upper limits (up to 80+-90+%), varying only by a few points, over a VERY long time... which could be MANY minutes. OR the System has decided PS is Not Responding.
In any case, whenever this happens, it means in all practicality PS CC is not working, so I either kill it or it's crashed.
Now, here's the thing: that VERY file, can immediately be opened in PS CS6 (which I have fortunately kept installed on my computer), and the mask will be as I thought it should be, and I can edit it as I always could, just fine! So it's obviously a PS CC thing, and I do NOT recall this happening prior to the JAN update. It is still a problem after the two subsequent updates.
I have not been able to determine the specific instances when this happens, as it seems to happen whenever I am editing a mask, no matter what size/softness/color brush, what magnification, what view mode, many or few layers, big or small file, etc.
I did upgrade my NVIDIA card (from GeForce GTX 260 [with current driver] to GTX660), just in case it was a factor (maybe kept it from crashing as fast? hard to tell... but it's still an unworkable problem). You can see from my Sys Info shown here from the PS CC Help menu that it should be more than sufficient for any PS CC task, and it's running the latest driver:
Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2664 MHz
Built-in memory: 16379 MB
Free memory: 12453 MB
Memory available to Photoshop: 14697 MB
Memory used by Photoshop: 60 %
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1200, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=2048
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
gpu[0].RendererID=4544
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3221"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20131219000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=1.16816e+011
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]
I work on digital-photography files, and use a layer mask in almost every file, so this relatively-recent bug is a big PITA, having to switch back and forth between CS6 and CC!
Until there's a fix... is there a way to roll-back my PS CC version to BEFORE the JAN 15, 2014 update?

I am not qualified to comment on technical issues; I'm just a user whose son in IT is my 'technical support department.' (But he's not much of a PS user.)
I'm pretty sure, however, that all my Prefs were set to the same things BEFORE the Jan 16, 2014 PS CC update as after (unless the update itself changed something I was unaware of... the settings APPEARED to be the same but I can't easily locate my notes of what my Prefs were from long ago).
And they were the same as the PS CS6 I have had installed on this same system for a very long time, with older video card with older driver, with newer driver; newer video card with newest driver, etc. Yet after that CC update, CC has not (until this workaround) worked re 'the masking bug' for me, yet CS6 has always worked just the same.
So I conclude that the only variable (other than the video card upgrade I did in an attempt to solve this and of course those Windows auto-updates) in this scenario IS something to do with PS *CC*, and after Jan 16, 2014.
As for restarting the machine vs. restarting PS, well, PS is the major player of my system, so when I shut that (and LR) down, I might as well 'clean things up' by Restarting. BTW, I am in the habit of closing and reopening PS (CC or CS6) whenever I finish with a file and load another, in order to get back some of that memory which PS never seems to want to let go. (This is not new to the latest versions, I think. My son says it's a 'memory hog'? ;-) ) I track its memory use in Windows' Task Manager and find that seems to let it 'refresh' itself. (See, I told you I'm not a technical person. ;-) ) But I do not think this has anything to do with the bug. Just a quirk of PS. Like when a tool goes all wonky (for example, its little icon becomes just a 'plus' sign even though the tool is still performing correctly, it's telling me, I think, that it would like to be restarted. And that makes it feel all better... I mean, tool icon reappears.)
Anyway... it's up to Adobe to figure out IF and what may be wrong with PS CC -- it still doesn't work for me as I had it configured at first, and I think it should, right? -- and to fix that... PLEASE. SOON.

Aperture keeps crashing on startup!

I recently moved my library with all referenced master to another 2TB drive. After doing that I imported a dozen of weddings and that took all the night.
After the import was done Aperture just crashes everytime on startup.
I tried with both repairing permission and database with no success, the REBUILD database seems to fix the problem for a while, but then it keeps crashing again just every time.
I don't think it's a drive problem, I run disk utility and at first there was some little problem with the disk which was soon fixed, now the disk is ok and I rebuilt the database several times already... what should I do now?
Anyone has the same problem?
ps. After database rebuild aperture keeps processing files on startup and crashes, what is that processing?
Thank you for your help.
Guido

Hi Frank,
I have a Mac Pro 8 intel core with 16 gig ram, OSX 10.6.8, Aperture 3.1.3.
The problem started presumably after the last import, was roughly 10,000 raw images from a DsmkIII and a mkIV.
No new software or hw installed but the HD which is an hitachi deskstar 7K3000.
After copying the lib and the masters from another drive i normally ran aperture so I guess importing all those images could have caused the problem, but Aperture is supposed to manage great amount of data...
If I create a new library everything works fine. The old library (the one I copied before importing) still works fine.
I get a crash report, never read it but the error code is something like BAD_ACCESS_ and other things..

Getting hang/crash problem when I try to close browser window from applet

I have a small Apllet that has a button that calls a Javascript function in the opening window, to close the window in which it is loaded.
The Applet window is a PopUp window from one of my application's window. First time I start my application and load that Applet the button works fine. It calls the Javascript method and the Method closes the window using the self.close() method.
But now if I open the applet window again and click on the button to close the windows, it hangs. I put in trace statements and saw that it hangs on JSObject.getWindow() window.
I am using JDK Plugin 1.4.2_07 and 5.0 , if I work out on IE browser, it works fine.But when I use firefox or mozilla it gives problem of hanging/crashing.
Note that in case of 1.4.2_07 this problem experienced some times but in case of 5.0 it gives always for other than IE browser.
Please, if somebody could give me some clue about why this would happen, I will really appreciate that. and code related to this is given below
import javax.swing.JApplet;
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
import netscape.javascript.JSObject;
public class TestApplet extends JApplet implements ActionListener{
protected JButton closeButton = null;
protected JSObject win = null;
private JFrame frame = null;
private boolean alreadyClosed = false;
public void init(){
this.win = JSObject.getWindow(this);
this.closeButton = new JButton("Close Browser Window");
this.add(this.closeButton);
this.closeButton.addActionListener(this);
frame = new JFrame("Test Frame");
frame.setSize(300, 400);
frame.addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {
System.out.println("windowClosing");
alreadyClosed = true;
TestApplet.this.stop();
frame.show();
public void actionPerformed(ActionEvent ae){
stop();
public void stop() {
if (!alreadyClosed) {
alreadyClosed = true;
frame.dispose();
closeLaunchedBrowser();
System.gc();
System.runFinalization();
private void closeLaunchedBrowser() {
final TestApplet thisObject = this;
Runnable r = new Runnable() {
public void run() {
try {
JSObject win = (JSObject)JSObject.getWindow(thisObject);
if (win != null && win.toString() != null) {
//win.eval("top.opener=self;self.close();");
//win.call("close", null);
win.eval("self.close();");
} catch (Exception e) {
Thread t = new Thread(r);
t.start();
Thanks.

I am waiting for any reply. I have tried for all these below options still I am getting Problem. I heard this is because of javascript, it wont call methods more times .Thats
why I need other than JSObject or java script solution.If some one know anything about this or any modifications I have to made for the below options to avoid that problem please let me know.
// URL durl = new URL(thisObject.getCodeBase(), "test/CloseMe.htm");
// System.out.println("URL :" + durl.toString());
// thisObject.getAppletContext().showDocument(durl);
// thisObject.getAppletContext().showDocument(new URL("javascript:window.close();"), "_self");
//win.eval("top.opener=self;top.close();");
//win.call("close", null);
//Object[] args = { "close", new Integer(50) };
// win.call("setTimeout", args);
//win.eval("setTimeout("close", new Integer(50));");
If it is the problem of JRE I just need it should work on 1.4.2_01 or higher.
thanks.

Aperture constantly crashing - esp. with HDR Efex Pro

I'm running Aperture 3.1.1 and OS 10.6.6. I've deleted the Aperture prefs, rebuilt the photo library, reinstalled Aperture, reinstalled OS 10.6.6, run all of the tests and repairs in Disk Utility and Onyx, and Aperture still crashes at frequent intervals whenever I'm editing - usually when painting something in or out with brushes. By far the most consistent crash is whenever I try to edit a photo with the HDR Efex Pro plug-in. I also get the spinning ball a lot, at fairly random intervals. The funny thing is that the HDR Efex Pro plug-in seems to work fine if I open Aperture in another user account although unfortunately my photo library is in my standard account and I'm reluctant to relocate it just to get a working version of Aperture. I've done everything suggested in Nik's FAQs (eg. deleting duplicate fonts), but nothing works. The Nik people have said I have a corruption in my user file which is beyond the scope of their support. I'm running a 24" 2.8GHz iMac with 4GB of RAM and about 20GB of free hard disk space. Aperture hasn't encountered many problems before recently, so my setup seems to have enough power. I have about 15,000 photos in the library (after importing my iPhoto library recently - by reference only) and the Aperture library is about 140Gb in size. If anyone has any suggestions for a fix, I'd be very grateful as I've run out of ideas. Thanks

Hi, I am no expert in Aperture 3 However just like you I had many issues and crashes of A3. My system is almost identical to yours and my A3 problems were the same as you. Like you, I tried all the fixes but still no luck. Yesterday, I went into my A3 Pref's / Previews & I changed the setting for "share with ilife and iwork" to never.
I haven't had a problem since but only time will tell if this is a total fix.
Good luck,
Art

Flash Builder 4.5.1 for Mac hanging/crashing during startup "Loading Workbench"

Hello,
I'm having ongoing trouble with Flash Builder 4.5.1 hanging/crashing during startup.
Sometimes the following Terminal command fixes the issue:
cd ~/Documents/Adobe\ Flash\ Builder\ 4.5/cascaded/308971/configuration/.settings
rm org.eclipse.ui.ide.prefs
However this isn't a silver bullet solution, and sometimes the only way is to uninstall and reinstall FB4.5.
But this is a major hassle, especially after 3 or 4 times!
I am running Mac OS X 10.7 and have updated to FB 4.5.1 Premium and also installed Subversion/Subclipse as well as the BlackBerry PlayBook SDK.
Problems seem to occur when working in SVN projects.
I have also noticed that the Delete and Arrow keys and Right Click fails to work sometimes also.
Is there a way to reset / clear FB 4.5 Prefs / Workbench?
Thanks,
David Douglas
Here is the console report below:
/Applications/Adobe/Adobe\ Flash\ Builder\ 4.5/Adobe\ Flash\ Builder\ 4.5.app/Contents/MacOS/Adobe\ Flash\ Builder\ 4.5 ; exit;
!SESSION 2011-09-13 15:07:58.914 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_26
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
Framework arguments: -keyring /Users/david/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/david/.eclipse_keyring -consoleLog -showlocation
!ENTRY org.eclipse.core.resources 2 10035 2011-09-13 15:08:02.101
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.ui 2 0 2011-09-13 15:08:02.905
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2011-09-13 15:08:02.906
!MESSAGE Commands should really have a category: plug-in='com.qnx.flashbuilder.multiplatform.qnx.ui', id='com.qnx.flashbuilder.multiplatform.qnx.ui.commands.OpenInfoCenter', categoryId='com.qnx.flashbuilder.multiplatform.qnx.ui.commands.category.help'

Delete the Adobe Flash Builder 4.5 folder from your Documents (assuming you don't have anything valuable in there). That seemed to work for me, as I don't keep my projects in there but there were some temp files that were breaking it. You'll probably have to re-inport your projects.
Adobe, I'm getting very sick of your (expensive) products wasting my time.

Both iPhoto and Aperture hanging up immediately on launch

Both iPhoto and Aperture hanging up immediately on launch..
Please help in resolving the issues

Report generated by Etrecheck:
EtreCheck version: 1.9.12 (48)
Report generated 24 July 2014 8:31:31 am IST
Hardware Information:
MacBook Pro (15-inch, Early 2011) (Verified)
MacBook Pro - model: MacBookPro8,2
1 2.2 GHz Intel Core i7 CPU: 4 cores
4 GB RAM
Video Information:
Intel HD Graphics 3000 - VRAM: 384 MB
Color LCD 1440 x 900
AMD Radeon HD 6750M - VRAM: 1024 MB
System Software:
OS X 10.9.4 (13E28) - Uptime: 0 days 0:14:47
Disk Information:
TOSHIBA MK7559GSXF disk0 : (750.16 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 749.3 GB (427.2 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
MATSHITADVD-R   UJ-8A8
USB Information:
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Computer, Inc. IR Receiver
Thunderbolt Information:
Apple Inc. thunderbolt_bus
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.ZTE.driver.ModemDriverMac (1.0.2d1) Support
[not loaded] com.ZTE.driver.ZTEUSBCDCACMData (1.3.33) Support
[not loaded] com.ZTE.driver.ZTEUSBMassStorageFilter (1.3.33) Support
[not loaded] com.lct.driver.LJACDDriver (1.0.0d1) Support
[not loaded] com.lja.driver.LJACDDriver64 (1.0.1) Support
[not loaded] lja.driver.USBModemCDC (1.0.0) Support
[not loaded] lja.driver.USBModemCDC64 (4.0.2) Support
[not loaded] lja.driver.USBModemData (1.0.0) Support
[not loaded] lja.driver.USBModemData64 (4.0.2) Support
Startup Items:
HWNetMgr: Path: /Library/StartupItems/HWNetMgr
HWPortDetect: Path: /Library/StartupItems/HWPortDetect
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.google.keystone.daemon.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
[loaded] com.oracle.java.Helper-Tool.plist Support
[not loaded] com.teamviewer.teamviewer_service.plist Support
[running] PPPMonitord.plist Support
Launch Agents:
[loaded] com.google.keystone.agent.plist Support
[running] com.lja.startupAgent.plist Support
[loaded] com.oracle.java.Java-Updater.plist Support
[not loaded] com.teamviewer.teamviewer.plist Support
[not loaded] com.teamviewer.teamviewer_desktop.plist Support
[running] Swapper.plist Support
User Launch Agents:
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.facebook.videochat.[redacted].plist Support
[loaded] com.fastestyoutubedownloader.TrialExpired.GoldFreeFirstWeek.plist Support
[loaded] de.metaquark.appfresh.plist Support
User Login Items:
PopClip
LockScreen2
Dropbox
Degrees
Internet Plug-ins:
JavaAppletPlugin: Version: Java 7 Update 60 Check version
FlashPlayer-10.6: Version: 14.0.0.145 - SDK 10.6 Support
EPPEX Plugin: Version: 10.0 Support
AdobePDFViewerNPAPI: Version: 10.1.10 Support
AdobePDFViewer: Version: 10.1.10 Support
Flash Player: Version: 14.0.0.145 - SDK 10.6 Support
Default Browser: Version: 537 - SDK 10.9
QuickTime Plugin: Version: 7.7.3
RealPlayer Plugin: Version: (null) Support
SharePointBrowserPlugin: Version: 14.0.0 Support
iPhotoPhotocast: Version: 7.0 - SDK 10.8
Safari Extensions:
Turn Off the Lights: Version: 3.0.0.12
Awesome Screenshot: Version: 1.4.3
AdBlock: Version: 2.7.7
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
Flash Player Support
Java Support
Time Machine:
Skip System Files: NO
Mobile backups: OFF
Auto backup: NO - Auto backup turned off
Volumes being backed up:
Macintosh HD: Disk size: 697.84 GB Disk used: 299.98 GB
Destinations:
Time Machine Backups [Local] (Last used)
Total size: 931.19 GB
Total number of backups: 2
Oldest backup: 2011-08-25 14:26:36 +0000
Last backup: 2013-10-23 11:24:28 +0000
Size of backup disk: Adequate
Backup size 931.19 GB > (Disk used 299.98 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
      7% WindowServer
      3% Safari
      1% hidd
      1% fontd
      1% com.apple.WebKit.Networking
Top Processes by Memory:
156 MB com.apple.IconServicesAgent
90 MB mds_stores
78 MB Safari
70 MB Dropbox
66 MB Finder
Virtual Memory Information:
911 MB Free RAM
1.49 GB Active RAM
616 MB Inactive RAM
1.01 GB Wired RAM
342 MB Page-ins
0 B Page-outs

Sql Developer hangs/ crashes while debugging

While happily debugging a piece of an SQL package using the remote debugger, I get a hang/crash on SQL devleoper. This occurs when I highlight a piece of code in the debugging window. The application freezes and has to be restarted using WindowsTaskManager.
Is this a reported bug? I was not able to find any discussion on the OTN forums or a quick google.
Regards,
Bill
Oracle SQL Developer 3.2.20.09
Version 3.2.20.09
Build MAIN-09.87
IDE Version: 11.1.1.4.37.59.48
Product ID: oracle.sqldeveloper
Product Version: 11.2.0.09.87
Version
Component     Version
=========     =======
Java(TM) Platform     1.7.0_17
Oracle IDE     3.2.20.09.87
Versioning Support     3.2.20.09.87
OS is Windows XP
Edited by: BillArms_GS on May 30, 2013 12:41 PM

We monitor these forums, but it's a unofficial place for bugs to be reported. Enhancements and bugs can be reported to My Oracle Support. You can also post your ideas up for other users to vote up at http://sqldeveloper.oracle.com
And thanks

Remote Desktop Services Manager Hangs / Crashes

Hi,
I have windows server 2008 R2 based remote desktop environment. When i access remote desktop services manager to manage domain users session, it hangs / crashes. I am not unable to add any other computer to manage as well. Same was working fine in Windows
server 2003.
Any valuable suggestion????
Regards
Rox_Star

Hi,
As a test, please create a new domain admin user account, log on to the server with it, and then open RDS Manager. Do you see the same issue with the new account?
Thanks.
-TP

Flash problems, by hanging/crashing in win7 64bit ?compatibility

Over the last two to three months I have had increasing problems with Flash Player and shockwave hanging/crashing. I use Windows 7 Home Premium 64 bit and Firefox. I understand that the latest versions of flash are not compatible with 64 bit Win 7. Is this true and how can I solve this problem? Thanks Drummond Mansbridge

They're 100% fully compatible with Win 7. At least on my Win 7 Ultimate 64 bit machine, there are no problems with FF, Opera, Safari, Chrome or IE 10.
Keeping BOTH Flash Player and Shockwave up to date, helps.
Flash Player Uninstaller
Flash Player Plug-in (All other browsers)
Shockwave Player Uninstaller
Shockwave Player 12 FULL Installer
Use those to do a complete uninstall and reinstall.
IF it still crashes frequently, check your other FF plugins to see if there's a conflict.

Aperture hangs on import from iPhone or camera

Since a few weeks I can't import from my iPhone or digital camera anymore.
If I try to import Photos from my iPhone or camera Aperture hangs forever. The Photos should be imported as referenced ones to a folder on a network share on a Mac OS X Server. This works fine, if the Picture source is i.e. a memory card or a HDD. And it has been working with the iPohne and camera before.
What happens is, that Aperture creates a file like "..importing.IMG0815.JPG" with 0 Bytes in the target folder. And than it hangs.
From this point on there is a permanent network traffic, and reasonable CPU load on both Macs (the kernel_task on the client and the AppleFileServer task on the Server). If I delete the "..importing.IMG0815.JPG" file it is instantly recreated. This continues even if I kill the Aperture application. The only way to stop this is to unmount the Network Volume.
Does anyone has an idea what this may cause?

sizzling badger wrote:
Aperture, Lightroom etc. are all designed to make use of direct import. They are safer than copying your files via the OS tools for the simple reason they access the cards read-only. If you use OS tools to copy then you are accessing the cards read-write which is far more dangerous if something goes wrong.
Culling your images during import saves time and disk space also. Copying your images directly and then importing is a WASTE OF YOUR TIME.
We disagree. Although such apps are indeed "designed" for direct import, my empirical observations since the earliest days of digital imagery have been that interacting indirectly using an app like Aperture is much, much less stable than directly interacting via Finder when properly done. One can peruse literally hundreds of digital image threads including this one to see overwhelming real-world evidence of what I am talking about.

Aperture hangs / crashes

Similar Messages

Maybe you are looking for