Skip navigation

Slow file open dialogue box

22932 Views 137 Replies Latest reply: Apr 3, 2014 6:16 AM by ADeweyan RSS
  • Michael Prescott Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 26, 2013 11:10 AM (in response to superjones)

    From my lay perspective, it seems Apple is working to move everything to the cloud rather than just providing clearly controllable options to enable cloud features.  It appears that at least a small amount data is going out of local network with every single file operation.  That this "bug" is less of a bug and more of a feature that is being actively developed.  That might explain well how it made it past testing.

  • brilor Level 1 Level 1 (20 points)
    Currently Being Moderated
    Dec 26, 2013 2:57 PM (in response to Michael Prescott)

    How many of the posters have iCloud turned off on their machine? Maybe ( and this is only a WAG with no real evidence to support it ) some of Apple's code assumes it is turned on. In my case iCloud is intentionally turned off.

  • gaijin5 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 31, 2013 2:51 PM (in response to brilor)

    I had this problem wiht iCloud turn on, so it doesn't seem related.

  • brilor Level 1 Level 1 (20 points)
    Currently Being Moderated
    Dec 31, 2013 3:24 PM (in response to gaijin5)

    gaijin5 wrote:

     

    I had this problem wiht iCloud turn on, so it doesn't seem related.

    Thanks for the feedback gaijin5.

  • Eric Hildum Level 2 Level 2 (265 points)
    Currently Being Moderated
    Jan 2, 2014 9:52 AM (in response to superjones)

    The reason this "bug" made it through all the testing is that it is almost certainly a configuration issue unique to the machines exhibiting the problem, not an actual bug in OS X. The workaround causes the automounter to skip mounting network volumes, so the issue is almost certainly related to a configured network share - likely a share that is no longer present for the computer to mount. Speculating - but possibly Finder is trying to follow aliases to remote volumes that are not responding or are responding slowly.

  • Michael Prescott Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 2, 2014 10:08 AM (in response to Eric Hildum)

    I have doubt about that.  I now have 3 pristine systems exhibiting the same behavior.  None are configured, just a basic clean installation, out of the box default behavior.

  • brilor Level 1 Level 1 (20 points)
    Currently Being Moderated
    Jan 2, 2014 10:35 AM (in response to Eric Hildum)

    Eric Hildum wrote:

     

    The reason this "bug" made it through all the testing is that it is almost certainly a configuration issue unique to the machines exhibiting the problem, not an actual bug in OS X. The workaround causes the automounter to skip mounting network volumes, so the issue is almost certainly related to a configured network share - likely a share that is no longer present for the computer to mount. Speculating - but possibly Finder is trying to follow aliases to remote volumes that are not responding or are responding slowly.

    A reasonable diagnosis but it doesn't match my circumstances and perhaps others too. There have never been any network shares attached to this Mac. I do mount some local external volumes ( and later eject them ) for clone backup. It is a standalone Mac.

     

    The live entries in my  /etc/autofs.conf are:

     

    AUTOMOUNT_TIMEOUT=3600

    AUTOMOUNTD_MNTOPTS=nosuid,nodev

    AUTOMOUNTD_NOSUID=TRUE

     

    Thanks for the input Eric.

  • zer0ed Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 2, 2014 12:11 PM (in response to Eric Hildum)

    Sure sounds like a bug to me. These complaints are coming from users who aren't using shares.  We are just using the default configuration files that come with a virgin install of Mavericks! No such problem existed in 10.8.x.

  • Eric Hildum Level 2 Level 2 (265 points)
    Currently Being Moderated
    Jan 2, 2014 10:16 PM (in response to Michael Prescott)

    Interesting. Are these really clean installs with no migration of any kind? Simply format hard drive and install Mavericks with no migration by Setup Assistant or Migration Assistant, and no network connections active - a pure install on a standalone system? And these are stock Macs with no third party hardware?

     

    If so, then check the Console for any messages which would indicate I/O issues to the hard drive, and Activity Monitor for unusual memory usage (e.g. memory pressure in yellow). Also verify the drive in stand alone mode or booted from the recovery partition.

     

    If there is no hardware issue, and a true clean install really does show an issue, then from the Terminal run

    sudo sysdiagnose -t Finder

    while duplicating the problem and submit the resulting diagnostic file and a System Report in a bug report to Apple with as complete a description of the symptoms as you can. Note that the resulting diagnostic file will be large, and will take some time to collect.

  • electrocuter Level 1 Level 1 (5 points)
    Currently Being Moderated
    Jan 3, 2014 1:15 AM (in response to d60Dave)

    Just adding a "me too" here. Experiencing a 15-20 second delay in Open and Save dialog boxes before file listings show up in the Open/Save window. System information: OS X 10.9.1, MacBook Pro 15" Retina (2013) with a 512 GB SSD.

  • Michael Prescott Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 3, 2014 5:32 AM (in response to Eric Hildum)

    From Apple-Merry Christmas-out of the box-day 1, clean systems.  On an older one, I took it down to the metal and started over twice.  I certainly have no hardware problems.  I can agree that I don't think it is a bug.  It is too pervasive, too obvious, and nothing unique or odd about our setups, so intuitions says it's half built or "surreptitious" feature that is still being tweaked.  I'm now at 10.9.1 also and prefer NOT to tweak system files to work-around it.  Just hoping Apple will change the behavior in the next patch.

     

    Used Windows exclusively for about 15 years, and got desensitized to a daily barrage of "security" patches and bug fixes.  When I switched to using OS X about 5 years ago, I was amazed with the quality and stability and usability.  So I feel like I can say from experience that in the last year to two, from my perspective, Apple has lost some integrity or quality or talent... whatever magic they had is going away FAST and they don't seem to be making an effort to correct or even acknowledge it.

  • zer0ed Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 3, 2014 6:11 AM (in response to Michael Prescott)

    Oh, it's a bug alright!

  • zer0ed Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 3, 2014 8:49 AM (in response to Eric Hildum)

    Eric, Sorry, I'm back to 10.8.5 but to answer your question:

    Yes, this issue was indeed happening on a newly formatted system drive with no migration whatsover, just a pure virgin install of Mavericks! Yes, I for one am running on a stock Late 2009 27" iMac 2.66Mhz Quad Core that suffers the symptom. We have a real issue here that many of us are experiencing with this Mavericks upgrade that did not exist in the previous releases of the OS! You folks seriously need to address this issue!

  • brilor Level 1 Level 1 (20 points)
    Currently Being Moderated
    Jan 3, 2014 10:42 AM (in response to Eric Hildum)

    Eric Hildum wrote:

     

    If so, then check the Console for any messages which would indicate I/O issues to the hard drive, and Activity Monitor for unusual memory usage (e.g. memory pressure in yellow). Also verify the drive in stand alone mode or booted from the recovery partition.

     

    sudo sysdiagnose -t Finder

     

    I filed a rdar( 15437435 ) with Apple on 11-Nov-2013 including console messages showing failures in the Open/Save panel code( failed assertions - not necessarily causing the problem but they show up when the problem does ) and error message from Preview.app( because I use Preview.app to test it ). The report includes a code snippet to reproduce the problem ( although it can be reproduced at will using Apple's Preview.app ), the workaround commenting out the auto_master file 'net' line and basic environment information.

     

    I've attached the sysdiagnose( btw: for folks who don't know, this is  a driver program that runs other unix programs --like lsof etc.---and collects the output ) output to the rdar

  • iching6 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 3, 2014 12:11 PM (in response to St. Clair Software)

    I think it is a defect in Mac OS.  The symptom occurs in both Mountain Lion and Mavericks.

    I had Parallels desktop running with Windows 8.1 and browsing or traversing through the directories are instant, while on Mac listing files in a directory is very slow, sometimes take up to over a minute!

     

    Apple should treat this issue seriously.  Apparenlty Windows 8 or 8.1 has a better scheme in caching without any obvious impact on initial perfomance.

     

    This issue bugs me since Mountain Lion and still not fixed.  I am using mid 2012 MacBook Pro Retinal with 750 GB SSD, 16 GB.

1 ... 3 4 5 6 7 ... 10 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (9)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.