Most likely his problem is due to his terminal (my guess: cmd.exe/powershell in Windows) and not his program code at all.
FWIW here's my non-reproduction of his problem, on Linux amd64, Sun Java 1.6.0, running in urxvt:
real 0m3.568s
user 0m0.616s
sys 0m1.152s
real 0m3.393s
user 0m0.648s
sys 0m1.060s
In other words, I could not reproduce the issue with the information he provided.I think adoption of a tool that just lets one share their dev environment would discourage this sort of due diligence, and encourage the useless "here's a dump of my code please fix it"-type questions.
While I know you were coming from a good place -- I'm all about automating a testable problem (i.e. TDD, write failing tests first), and I think in the right hands, this would be a nice tool -- I could only see SO using this to further enforce strict requirements in what they consider a "valid" question.
"You must set up a lab environment that fully replicates the issue in question."
Maybe they wouldn't let it go that far (I would hope), but I think it would head in that direction.
Disagree. OP failed to exclude some possibilities by doing multiple randomized trials and so on (or at least stating whether he had done so), but he supplied the source code and a description of the behavior that was perfectly adequate to understand the issue. Nothing personal, but your post above is the epitome of deflecting a question instead of engaging with it.