There is a new beta version of BSF4ooRexx available on Sourceforge for all operating systems: <https://sourceforge.net/projects/bsf4oorexx/files/beta/20161026/>.
There is (temporarily) an external Rexx function named BsfApplyHotFixCrash( | .true | .false) available. That "hot fix" does nothing else but releaste the thread's time slice for 1/10 of a second right before doing a Rexx AttachThread() in two cases: if a message from Java to a Rexx object is processed or a Java rooted Rexx program gets run. With this version the JavaFX crash test application in <https://www.dropbox.com/sh/xjnzwm6r0qnugzc/AACN67fJc4CZ2NOYxNaSiewFa?dl=0> crashes on 32-bit Windows when running via "startTestProgressBar.rex", but usually completes successfully (!) when running via "startTestProgressBar-using-HotFix.rex", which does nothing else but activate the aforementioned "hot fix"! So the crashes semm to have to do with AttachThread() in one way or another. --- It is my take that the observed crash is caused by ooRexx. It seems that at least two Rexx interpreter instances need to be running. According to all stack traces they are rooted in an AttachThread(). The above test case is the best one I can come up with which causes the crash relatively early in the process. ---rony P.S.: The above directory is located in <https://www.dropbox.com/sh/a86bt042pravm5p/AADK9Fac5pobhscxKxrRRxkua?dl=0> in the subdirectory named "20170807-testApp". ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
