Ah, but there's something to be said for the effectiveness of these weird error messages. Typically the conversation would go: "We got an error come fix it", with no further details. It can be really hard to track down from there.

I experienced something similar when troubleshooting some Chrome issues across a Citrix XenApp farm. It was so incredibly useful to be able to ask the users "Did you get a dinosaur or a He's Dead Jim?" One was a connection issue I could disregard, the other was the memory management problem I was trying to track down.

Sometimes I wonder if we should make all our cryptic, developer-only errors absurd and memorable. I've never had a user tell me anything like "java.lang.OutOfMemoryError: Java heap space error". "The lemur jumped the shark again" gets their attention.