‘File :///’ bug fixed in Apple’s latest OS X developer release

Apple today released a new OS X build to AppleSeed (build 12D65) and the obscure, but nasty ‘File :///’ bug is no longer present, sources say.

So, no more instant application crashes.

And, yes, we know there’s an extra space in there, but we couldn’t type the real thing without crashing Safari!

It’s good to see Apple so quickly working on a fix for this weird little bug.

[Thanks to MacDailyNews readers too numerous to mention individually for the heads up.]

22 Comments

    1. I was trying it in the address bar, and it would just open the Finder to the desktop. So, I was posting to say I had 10.8 and couldn’t replicate, and in the process typed the phrase that shall not be typed in the comment box, and sure enough; instant spinning beach ball. Try it with a capital ‘F’.

    1. I always think its funny when someone makes a big deal.. or trolls about little bugs in the Mac OS.. as if Windows is free of bugs.

      Hell… one could write a book on the useless error messages Windows spews out.. “please contact your system administrator..” I AM THE SYSTEM ADMIN!!! lol.

        1. I’ve posted my POV elsewhere in this thread.

          But I will entirely agree that growing organizations lose track of their actual ‘organization’ and are continually in a state of repair. The horror of dealing with the staff at the iTunes and Mac App stores is a terrific example. I can also point to the messes created by Apple’s documentation scheme where the right hand rarely knows what the left hand is doing. The documents for AirPort Utility v5 and v6, after a clamoring of anger from users, still remain profoundly WRONG.

          There is no such thing as perfection. There are only varying levels of attempted perfection. Apple has NEVER been known for absolute perfection, seeing as that’s impossible. Apple just does things better than everyone else.

          Except for… 😉

    2. From the end user license that’s been around for decades, maybe even a decade before Tim Cook joined Apple:

      7.4 APPLE DOES NOT WARRANT AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE APPLE SOFTWARE AND SERVICES, THAT THE FUNCTIONS CONTAINED IN, OR SERVICES PERFORMED OR PROVIDED BY, THE APPLE SOFTWARE WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE APPLE SOFTWARE OR SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT ANY SERVICE WILL CONTINUE TO BE MADE AVAILABLE, THAT THE APPLE SOFTWARE OR SERVICES WILL BE COMPATIBLE WITH THIRD PARTY SOFTWARE OR OTHER THIRD PARTY SERVICES, OR THAT DEFECTS IN THE APPLE SOFTWARE OR SERVICES WILL BE CORRECTED.
      7.5 YOU FURTHER ACKNOWLEDGE THAT THE APPLE SOFTWARE AND SERVICES ARE NOT INTENDED OR SUITABLE FOR USE IN SITUATIONS OR ENVIRONMENTS WHERE THE FAILURE OR TIME DELAYS OF, OR ERRORS OR INACCURACIES IN THE CONTENT, DATA OR INFORMATION PROVIDED BY, THE APPLE SOFTWARE OR SERVICES COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE, INCLUDING WITHOUT LIMITATION THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, LIFE SUPPORT OR WEAPONS SYSTEMS.

      1. Every EULA has similar wording. I doubt there is a single piece of software written that doesn’t have it.

        I absolutely despise this particular wording in EULAs. EULAs are probably the most anti-consumer, bill-of-goods sold to people.

        Can you imagine any other everyday manufactured product coming with a notice that said something like this.

        Can you imagine Ford putting a sticker on new cars that said: FORD DOES NOT WARRANTY THAT YOU WILL ENJOY DRIVING YOUR NEW CAR, THAT THE CAR RADIO WILL WORK, THAT THE TRANSMISSION WILL WORK, THAT THE CAR WILL GET YOU TO WORK ON TIME, OR THAT THE CAR WILL EVEN START.

        Other manufacturers give consumers warranties and/or guarantees… computer/software developers give us disclaimers.

    3. Apple is never perfect. They’re just better than everyone else.

      And I am inspired to quote myself:
      Modern coding is well beyond the comprehension of any one person.

      Most modern coding requires group development.
      IOW: Creation-By-Committee.

      As the old saying goes:
      No masterpiece was ever created by committee.

    1. What made it nasty was it could shut down the console app if you played too much with the bug…otherwise ..it was just really obscure and had been around for a while until anyone noticed it 😉

  1. It definitely crashed every app I tried it in. If you are typing it into safari and seeing the desktop you are most likely using a lowercase “f”. I did that the first time I tried it also.

  2. Definitely imagine that which you said. Your favorite reason appeared to be at the net the simplest thing to have in mind of. I say to you, I definitely get annoyed even as other folks think about worries that they just do not understand about. You controlled to hit the nail upon the highest and defined out the whole thing without having side effect , other people could take a signal. Will probably be again to get more. Thank you

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.