Previous 1 2 3 4 5 6 Next 154 Replies Latest reply: Apr 26, 2015 8:05 AM by polarbreeze1 Go to original post
  • valrus Level 1 Level 1 (0 points)

    Thanks for the workaround. Mad helpful. I reported to Apple as has been requested several times as well.

  • Gonzoandrea Level 1 Level 1 (0 points)

    Same problem for me.

    Just tried to fix it with Snaggletooth_DE's fix and wait to see what will happen.

    Hope things get better for me and for Apple developers too...

     

    thx

  • Polira Level 1 Level 1 (0 points)

    This fix worked for me as well.  Thanks.

  • Gonzoandrea Level 1 Level 1 (0 points)

    After few days of testing, I can say that this workaround is f***ing awesome!

  • d60Dave Level 1 Level 1 (10 points)

    I applied the workaround too and it has definitely improved things but unfortunately previews of image files still take longer than they should to appear when using the column view which I mainly use.

     

    C'mon Apple, lets have a proper fix for this.

     

    Dave.

  • brilor Level 1 Level 1 (20 points)

    d60Dave wrote:

     

    C'mon Apple, lets have a proper fix for this.

    Apple does NOT monitor these lists, please submit feedback and bug reports to Apple for this issue. Thank you

  • brilor Level 1 Level 1 (20 points)

    Gonzoandrea wrote:

     

    ... this workaround is ......awesome!

    Yep, and remember it is only a workaround. Please consider submitting feedback and a bug report to Apple for this issue. Thank you

  • d60Dave Level 1 Level 1 (10 points)

    - Already have thank you, several weeks/months ago.

  • nikalan Level 1 Level 1 (0 points)

    Problem solved and problem reported. Thanks a lot. Hope it works until they fix it.

  • MindFad Level 1 Level 1 (0 points)

    10.9.1 installed. Same deal, no change. Oh well.

  • brilor Level 1 Level 1 (20 points)

    atpyburn wrote:

     

    but I'm not familiar with "commenting out" items

    "commenting out" is programmer's terminology for making an active line of code inactive. It typically means a language compiler ( such as C, Objective-C, Fortran etc. )  ignores the line of code when an app  it is built ( i.e. compiled and linked ). In this particular case 'automount' consults the auto_master file and ignores any lines prefixed with the pound sign ( # ). The reason for  "commenting out" is most languages have a symbol to deactive a line of code or to write comments describing the function of the code. So deactivating turns it into a comment ---thus commenting out.

  • Michael Prescott Level 1 Level 1 (0 points)

    Stumbled into this thread after experiencing this problem with Finder being slow.  I've seen it for months now and figured it was due to some system file being corrupted on my old Mac.  I've now got a pristine new system and the old system completely refreshed to give away for Christmas gift.  Anyhow, both systems are exhibiting this behavior.  Taking way too long to simply list files in a folder.  I was finally driven here when even applications like SublimeText are failing to list project files... surely rooted in the same Finder problem.

     

    Here's another tidbit I've noticed.  Every time Finder does it's little busying thing, my firewall is revealing it is sending out packets.  What is up with that, and what does

    "I can't say too much due to NDAs"  mean?

  • brilor Level 1 Level 1 (20 points)

    Michael Prescott wrote:

     

    ...what does "I can't say too much due to NDAs"  mean?

    NDA = Non-Disclosure Agreement - a binding legal agreement between Apple and developers.

    Apple's Developer Program allows developers to download unreleased/in-development ( i.e. alpha/beta stages ) Apple software ( typically OS X and developer tools ). The program requires: (1) a membership fee ( $99 ) and (2) legally forbids disclosure to the public of anything the developer might find during testing of Apple's beta software.

     

    So those comments mean the developer knows whether the upcoming OS X point release solves a problem but is compelled to not reveal it.

  • Michael Prescott Level 1 Level 1 (0 points)

    I see.  Thanks!  That's good news, I think. 

     

    I expected this new system to be amazingly fast, but this Finder bug is ubiquitous.  Affecting every application, every operation.  It'll be a relief to have it fixed.

  • superjones Level 1 Level 1 (0 points)

    Yeah. For such an annoying issue that affected every application that opens or saves files from/to disk, it was indeed nice to see a mention of "NDA" regarding this issue and its workaround prior to the release of 10.9.1. Too bad it was not fixed with 10.9.1...

     

    It is strange to me that an issue like this made it through all of the developer testing, GM, GA, and still with the first major update. Did not a single tester or Apple developer work on figuring this out for months upon months? Maybe no one tried opening or saving a file with any application during testing? Did 10.9 follow the waterfall model with very little emphasis on V&V?

     

    I have reported several bugs for 10.9, I have worked with Apple Care, and developers focus on whatever and Apple Care support engineers know nothing and have provided no resolutions or workarounds. I always find my answers online or on my own when I encounter a problem that isn't documented as FAD in some Apple doc.

     

    OS X is still far and away my preferred OS for personal use, but I must say that I am growing somewhat dissatisfied with the lack of meaningful updates for OS X 10.9 that address real issues that impact a most if not all users. Two updates from Apple released with fixes for Gmail connectivity means nothing to me as I have never had any issues with Thunderbird connecting to Gmail (even when left open and accessing Gmail on my iPad and/or iPhone) or any other IMAP or POP3 email server ever -- using OS X Mail is like using Outlook Express and if there are problems using Gmail with the default Mail.app, then let users find and use something better. It seems to me that problems for some users a stock OS email client working with a Google service is not as big of a priority as the fastest of the fastest computers taking many seconds to display the contents of indexed folders. And what about choppy animation for Disk Utility when launched (not to mention the missing "OK" message when verifying the primary disk/partition), or timing of authentication for Twitter and iMessage when Notification Center first launches, and why such an increased memory footprint for kernel_task and the seemingly unusual memory consumed by com.apple.IconServicesAgent, and so on?

     

    The task of resolving systemic issues that affect most or all users of OS X should not always result in workarounds discovered and delivered by the user community. Maybe 10.9.2 will fix some things, or maybe the most meaningful change delivered will just be a buggy initial iteration of FaceTime Audio for OS X.

     

    This issue lasting this long has been very irritating and this is all I have to say about it for now. I remain thankful that someone was able to discover and share a workaround while Apple's own support and developers did and do nothing.

Previous 1 2 3 4 5 6 Next