Comment 27 for bug 1472755

OK, I think I finally found it. There are some dummy loggers in the run time that I added because some of the unit tests run without a fully initialized run time (which provides access to the logger), but still need a working logger. For these tests, a global dummy instance is used. It's the clean-up of the dummy instance that causes the problem because, depending on global destructor ordering, the instance may have been destroyed at the time the atexit handler tries to finalize it.

Not sure what the best fix is yet. Working on it...