My Macbook Pro 15" Retina (mid-2012) has been crashing to login screen several times per day since I installed Yosemite. Appears especially with an external display connected and always at a very random moment. Never experienced this on Mavericks. Looking at the WindowServer*.crash logs in the Console application, the reason is always something like this:
...
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000032
VM Regions Near 0x32:
-->
__TEXT 000000010d8bd000-000000010d8be000 [ 4K] r-x/rwx SM=COW /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/WindowSe rver
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreGraphics 0x00007fff92af839d color_space_get_md5_digest + 24
1 com.apple.CoreGraphics 0x00007fff92fcd8f5 color_space_get_identifier + 9
2 com.apple.CoreGraphics 0x00007fff92e16a47 CGXColorSpaceRegistryCopyRegisteredColorSpace + 42
...
After some googling, I decided to reset the NVRAM on my laptop by pressing Cmd+Option+R+P at bootup (as described here: How to Reset NVRAM on your Mac - Apple Support). I haven't experienced a single crash for 3 days now. It's still too early to say the problems are gone but looks promising.
I work at three different locations, using three different external displays. The problem was much more frequent on one of the models where I was using a custom calibrated color profile. Since the crash logs indicate the problem is always related to color conversion, I also switched from the custom calibrated profile to a standard "Color LCD" profile for that display. However, OS X still picks a model specific profile for the other two displays and still no crashes on those either. So I tend to believe it was the NVRAM reset that did the trick rather than the display profile change. Not 100% sure though.
Stay tuned...