#946 Rexx crashes and stops executing


From Application Event log--"Faulting application rexx.exe, version, faulting module rexx.dll, version, fault address 0x000322c3."
After this crash no rexx code is executed. I have an app that spawns short runnning rexx routines. After the crash rexx routines start but not executing. They will stay in memory until the server runs out of memory (at about 600 rexx processes) and crashes. If I get on in time to kill all rxapi.exe processes then everything goes back to normal without a change to the application. I have a monitor now that kills rxapi.exe processes when the number of rexx processes reaches a threshold--it seems to help. I need a resolution until my management forces me to get away from rexx as an unsupported product. This started happening after I upgraded from 3.2.0 to 4.0.0 (really bad problems) and then to 4.0.1. The current release is better but I still have a problem about twice a week.
Thank you.


  • ykorenfeld

    ykorenfeld - 2010-10-04

    The environment it Windows 2003 SP3, 4 GB of RAM, 4 CPUs

  • Mark Miesfeld

    Mark Miesfeld - 2010-10-04

    The ooRexx development team appreciates people taking the time to open up bug reports, thank you.

    We need some way of reproducing your problem. The best thing to do is attach an example program that reproduces the problem to this bug report. The information from the Application Event log has no real meaning.

  • ykorenfeld

    ykorenfeld - 2010-10-06

    I now believe it is a duplicate of 3080931 caused by a memory leak.



Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks