If I’m following correctly, the latest 9.0 is 9.0.0.638, and has the presumed fix for the OOM that we should have currently in the private build 9.5.0.100. But that won’t have logging, and there is no reason to expect that it addresses the OOM at this point any more that the 9.5.0.100 we are currently running. If I am not missing something, all that would be gained by going to *.638 would be to confirm that it reproduces on the latest 9.0 build, or the unlikely outcome that it somehow fixes this new repro by chance.
The latest email I have in that chain is from you on 1/5/16 with a build that addresses the shape file regression. I don’t think it has the logging at that point. Before that is .9.1.0.175 attachment on 12/17/15 , but that one is also not looking like it would have the logging. I never did find one that was clearly containing the logging. These versions are all confusing, especially over a year later. Looks like that ends the emails that I have saved. And because it was a diagnostic test, it was never put into our source control. I’ll look through my disk backups to see what I can find, but not hopeful.
I just found strong named 9.1.0.100 on 10/6/15. I think that’s the latest with logging. But then it reoccurs to me that we are getting the exception with a new call stack in the “fix” version. So just grabbing this older logging version won’t really help since it’s the subsequent resulting fix that is currently reproducing.
