Multithreaded so ware is typically built with specialized "concurrent objects" like atomic integers, queues, and maps. ese objects' methods are designed to behave according to certain consistency criteria like atomicity, despite being optimized to avoid blocking and exploit parallelism, e.g., by using atomic machine instructions like compare and exchange (). Exposing atomicity violations is important since they generally lead to elusive bugs that are di cult to identify, reproduce, and ultimately repair.In this work we expose atomicity violations in concurrent object implementations from the most widely-used so ware development kit: e Java Development Kit ( ). We witness atomicity violations via simple test harnesses containing few concurrent method invocations. While stress testing is e ective at exposing violations given catalytic test harnesses and lightweight means of falsifying atomicity, divining e ectual catalysts can be di cult, and atomicity checks are generally cumbersome. We overcome these problems by automating test-harness search, and establishing atomicity via membership in precomputed sets of acceptable return-value outcomes. Our approach enables testing millions of executions of each harness each second (per processor core). is scale is important since atomicity violations are observed in very few executions (tens-hundreds out of millions) of very few harnesses (one out of hundreds-thousands). Our implementation is open source and publicly available.CCS Concepts: •So ware and its engineering → So ware testing and debugging; So ware reliability; Consistency;