Everyone has a test environment.Yup, the weird bugs are rarely ever found in the test/dev/staging/qa environments. Sometimes it takes longer to even figure out how to reproduce some odd bug a customer found in Prod.
As one example we had one blade server that was causing financial data corruption. The senior java developers and architects debugged java down to the CPU and found 1 CPU core that was making mathematical errors under specific conditions. This would never in a million years have been found in dev, test, staging, QA, pre-prod environments. I was given the instruction by leadership to "drive over the server" in the parking lot as neither upstream OEM's were interesting in debugging it further.
Another fun one I ran into was using VLAN tagging on CentOS 5 on specific hardware with a specific NIC of whom shall not be named could get into a situation where partial frames were being transmitted in a loop from the ring buffer at the highest physical packet rate of the NIC which is surprisingly very fast. It brought down the access switches and the very big distribution routers. We debugged it pretty far down but hit a wall when one of the three vendors involved would not sign the 3-way NDA. The NIC was not Intel.
Or here is another one. We had a multi-million dollar storage solution that was never needed and in production it caused an IO fencing issue that broke the production databases in a glorious way. That bug would never have been tickled in dev or staging. It required a specific series of failures in the storage that triggered a logic failure on their controller of raid controllers. The vendor should have caught this one.
I could probably write a book about all the weird bugs that "should never happen" but only happen under real-world Production use cases.