On 22.11.2021 18:11, Rick McGuire wrote: > I'm not sure what in that particular line could cause a crash, but it might > be because we do the > reinitialization every time an interpreter instance is created. Those are > thing that should only > be one once per process, so I rearranged the code a bit.
thank you, that fixes it! ---rony > > On Mon, Nov 22, 2021 at 11:37 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at > <mailto:rony.flatsc...@wu.ac.at>> wrote: > > On 22.11.2021 17:15, Michael Lueck wrote: > > Greetings ooRexx'ers, > > > > Rony G. Flatscher wrote: > >> Just filed a bug (with the code attached) at > <https://sourceforge.net/p/oorexx/bugs/1789/ > <https://sourceforge.net/p/oorexx/bugs/1789/>>. > > > > > > So I read through that thread... seems possibly Rick spotted the defect > in Rony's code, and > > therefor cleared ooRexx of any defect in this area? > > No. > > My test code was without Java trying to mimic what happens in the Java > based web server (so > the code > was created ad hoc from scratch, is relatively complex and I have > permutated it over the weeks and > in one scenario got a crash that I reported with the code). The > termination of Rexx interpreter > instances (rii) occurred in a native method but in the context of the > very same rii, which > caused in > this scenario the crash (due to exhausted system resources). > > The true ooRexx crash occurs in a different scenario running in a Tomcat > (Java) process. Today I > became able to create mini dumps on the Java web server in case a crash > occurs. This is what I > reported today (the error message is: "Unhandled exception at 0x634D8CE1 > (rexx.dll) in > hs_err_pid1628.mdmp: 0xC0000005: Access violation reading location > 0x00000000." ) in the e-mail > subject changed to "MSVS MiniDump created, more concrete infos ...". > > ---rony >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
