Macs are Stable :)

[SYNACK]

Typing These 8 Characters Will Crash Almost Any App On Your Mountain Lion Mac - Slashdot

All software has bugs, but this one is a particularly odd one. If you type "File:///" (no quotes) into almost any app on your Mac, it will crash. The discovery was made recently and a bug report was posted to Open Radar. First off, it’s worth noting that the bug only appears to be present in OS X Mountain Lion and is not reproducible in Lion or Snow Leopard. That’s not exactly good news given that this is the latest release of Apple’s operating system, which an increasing number of Mac users are switching to. ... A closer look shows the bug is inside Data Detectors, a feature that lets apps recognize dates, locations, and contact data, making it easy for you to save this information in your address book and calendar.

[Roberto]

Just tried it here and they're not wrong. Big oops. It crashes finder & Safari, which is especially daft because that's the two main apps where you might legitimately type that while trying to do something. Big cock up on Apple's part.

[CAM]

Does it work if you click it?

[SYNACK]

Does it work if you click it?

Apparently it only works in a text input field where it can be parsed by an osx system library and only with the capitalised version.

[rich_tech]

sounds like something that you can expect a hotfix for sharpish there then

[Arthur]

Does it work if you click it?

Try this instead...

grack.com/hangsafari.html

or

mailto:foo@bar.com?subject=File:///&body=File:///

or

Type File:/// into Spotlight

Btw, turning off the spell checker will stop your Mac from crashing.

[SYNACK]

sounds like something that you can expect a hotfix for sharpish there then

It's no where near as bad as the; doesn't bother checking passwords bug or, the stores your passwords in plaintext debug logs bugs. Those took some time to be patched, I can't imagine this one taking a higher priority, still a fun game for any Apple store patrons until then

[Arthur]

still a fun game

Indeed...

[SYNACK]

Indeed...

What's sad is that while this is an old joke but still would not work on our SMS, not because they sanitise their inputs but because the whole 3GB monster is based on three loosely linked Access 2003 databases. Now that's a joke

[Arthur]

the whole 3GB monster is based on three loosely linked Access 2003 databases.

That sounds like a nightmare waiting to happen, especially once all three DBs reach a combined size of 6GB.

[SYNACK]

That sounds like a nightmare waiting to happen, especially once all three DBs reach a combined size of 6GB.

Yea, that is without student photos or anything, the main file size killers are all the VB exe files and ancient DLL libraries, the system files install still choke out on 64bit systems because it tries to register a 16bit graphics library. The DB sizes expand rapidly when you have a hundred users all accessing the MDB over the network.

It even has a well known back door password in their online documentation. Still it doesn't crash when you type File:/// into it so it's not all bad

[Arthur]

IMO, the random crashes in Android 4.2 are much worse than this Apple bug because at least with the latter you can simply avoid typing File:/// into any text boxes. With Android, you're stuck with them until Google can be bothered to fix them.

[SYNACK]

IMO, the random crashes in Android 4.2 are much worse than this Apple bug because at least with the latter you can simply avoid typing File:/// into any text boxes. With Android, you're stuck with them until Google can be bothered to fix them.

Oh, that looks like my Nexus 7 which I replaced and got one that glitches the screen with weird lines when using a browser as well as being slow and crashy like the last one, I don't know how it became so popular. Angry Birds must be VERY addictive.

[Rozzer]

lol thats an interesting bug!

[CyberNerd]

IMO, the random crashes in Android 4.2 are much worse than this Apple bug because at least with the latter you can simply avoid typing File:/// into any text boxes. With Android, you're stuck with them until Google can be bothered to fix them.

How do you get that logfile? I want to check mine - but I've not noticed it crash at all - I've rebooted it 3 times (in two months) and use it for long periods when playing ingress.