Of course, that one was gotten because it's simply the title of a song, mapped to lower case with spaces removed.
Password phrases, even if long sentences, must not be something pulled from popular culture.
I wouldn't expect, say, "thequickbrownfoxjumpedoverthelazydogs" to hold up.
I bet you that it woudn't have been cracked, had the user had changed a few words in a way that is easy to memorize. I would have changed "stripper is crying" to "stripper is dichloromethane". (Compound used as powerful paint stripper.)
I'm assuming last.fm does not support blanks in their passwords since none of these passwords use that character. Or perhaps very few people realize you can use that character to help make passwords more manageable.
My recommendation to people who ask the past few years has been full, grammatically correct sentences.
Some let you fill out the form and then click on submit and tell you a problem with your password or something. You change it, then they tell you it has to be shorter than 15 or 10 characters, and impose such conditions you almost wait for them to tell you "use: 2Hx,!rJ" as your password. Some don't even support "special" characters, spaces, or hyphens. By the 4th or 5th attempt to register, you're basically trying to come up with the stupidest password you can to feed this monstrosity.
Mind you, somme of these are big companies websites. I think password or registration management also affects things like talent acquisition. Companies using Taleo for instance are doing a great job of repulsing normal, mentally sane, people. The whole approach of registering one account for each company on a different company subdomain on the same domain (company1.taleo.net, company2.taleo.net) and for each one fill out the profile all over again is beyond the realm of my comprehension.
The browser asks you to save the password/username for the website, but it does so for the domain, not the subdomains which all have different passwords. I give up on a company if it's using Taleo. I'm not talented or competent, but I'm sure really competent people wouldn't want to put up with this either and it hurts recruiting.
This sounds like your browser's password manager's problem, namely assuming that users will only have a single password per top-level domain.