Looking at this in the debugger, the main method is requesting the result from a message object, and is waiting because there message is not complete. However, the only other Rexx threads are a couple that are in the thread pool waiting to be dispatched. I suspect there might have been an error in the dispatched message object such that the thread died without a the message completing.
Rick On Thu, Nov 19, 2020 at 12:00 PM Erich Steinböck <erich.steinbo...@gmail.com> wrote: > With the current trunk we have a hang issue on Windows when running the > tests that I cannot track down. > > I have no idea what may have introduced (or surfaced) the issue, and the > issue seems elusive as if it were related to GC. > > The fastest way to reproduce is by running > testoorexx -s -S -f SysFileTree -f Section1 > > Help very much appreciated! > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
