Random Classic Appserver Memory violation error 49 on Linux 

Random appserver memory violations have been happenign in the application for a few weeks.
The problem always seems to happen in the same class file and there haven't been any changes made recently.

When the problem happens the protrace file contains a stack referencing line -1:
 

--> com.demo.dev.class.FailedFixed at line -1 (com/demo/dev/class/FailedFixed.r)
ChildAppprog.p at line 15836 (ChildAppprog.r)
SomAppprog.p at line 10663 (SomAppprog.r)

The full stack trace generated by the appserver is:
 

#1   [0xacc7b7] uttraceback+0x37  from /usr/dlc/bin/_proapsv
#2   [0xacffe7] uttrace_withsigid+0x1f7  from /usr/dlc/bin/_proapsv
#3   [0xad0285] utcoreEx+0xd5  from /usr/dlc/bin/_proapsv
#4   [0x47c438] drexit+0x388  from /usr/dlc/bin/_proapsv
#5   [0x96d001] drSigFatal+0xa1  from /usr/dlc/bin/_proapsv
#6   [0x3d8ef980] __restore_rt+0x0  from /lib/x86_64-linux-gnu/libpthread.so.0
#7   [0x851aed] rnproc_entry_reuse+0x59d  from /usr/dlc/bin/_proapsv
#8   [0x8396c7] rninterpret+0x37  from /usr/dlc/bin/_proapsv
#9   [0x80a2d2] loadRcode+0x142  from /usr/dlc/bin/_proapsv
#10  [0x80e7d4] rnloadObject+0xa84  from /usr/dlc/bin/_proapsv
#11  [0x80f76c] rnNew_Func+0x1ec  from /usr/dlc/bin/_proapsv
#12  [0x4a9f9c] fmNEWOBJ+0x4c  from /usr/dlc/bin/_proapsv
#13  [0x4c3616] fmeval+0x256  from /usr/dlc/bin/_proapsv
#14  [0x4c3872] fmeval+0x4b2  from /usr/dlc/bin/_proapsv
#15  [0x7f9e61] rnasgsupersimple+0x141  from /usr/dlc/bin/_proapsv
#16  [0x83851a] rnexec_entry+0x18a  from /usr/dlc/bin/_proapsv
#17  [0x8396c7] rninterpret+0x37  from /usr/dlc/bin/_proapsv
#18  [0x42cea7] cr_run_loaded+0x37  from /usr/dlc/bin/_proapsv
#19  [0x42f5e8] execProc+0x5f8  from /usr/dlc/bin/_proapsv
#20  [0x42f9e3] execCall+0x23  from /usr/dlc/bin/_proapsv
#21  [0x434fac] WriterOutputRequest+0x35c  from /usr/dlc/bin/_proapsv
#22  [0x435b4a] open4GLRead+0xba  from /usr/dlc/bin/_proapsv
#23  [0x435fe5] ub_sendRsp+0x125  from /usr/dlc/bin/_proapsv
#24  [0x437021] ub_processRequest+0x1f1  from /usr/dlc/bin/_proapsv
#25  [0x43dfde] csd_dispatch_message+0x1ae  from /usr/dlc/bin/_proapsv
#26  [0x43c1e0] classicapsv_main+0x3d0  from /usr/dlc/bin/_proapsv
#27  [0x43c55e] main+0x3e  from /usr/dlc/bin/_proapsv
#28  [0x3c792c87] /lib/x86_64-linux-gnu/libc.so.6
 

The appserver logs contain:

Server:
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- SYSTEM ERROR: Memory violation. (49)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- ** ABL Debug-Alert Stack Trace **
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- --> com.demo.dev.class.FailedFixed at line -1 (com/demo/dev/class/FailedFixed.r)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- ChildAppprog.p at line 15836 (ChildAppprog.r)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- SomAppprog.p at line 10663 (SomAppprog.r)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- ** Save file named core for analysis by Progress Software Corporation. (439)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- ** ABL Debug-Alert Stack Trace **
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- --> com.demo.dev.class.FailedFixed at line -1 (com/demo/dev/class/FailedFixed.r)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- ChildAppprog.p at line 15836 (ChildAppprog.r)
[22/07/12@08:37:35.467+0100] P-015574 T-1039278272 1 AS -- SomAppprog.p at line 10663 (SomAppprog.r)

Broker:
[22/07/12@08:37:36.060+0100] P-004806 T-S-0046 1 UB ----------- ServerSocketsIPC read() IOException : java.io.EOFException : NULL (8127)
[22/07/12@08:37:36.063+0100] P-004806 T-S-0046 1 UB ----------- ServerIPCException in getServerIPCMsg() : ServerIPC error: ubServerSocketsIPC.read() IOException: null. (8119)
[22/07/12@08:37:36.086+0100] P-004806 T-S-0046 1 UB ----------- Posted EAbnormalShutdownServerEvent for PID: 15574
[22/07/12@08:37:36.087+0100] P-004806 T-C-0041 1 UB ----------- Server Terminated Abnormally (8420)

The exact cause is not known at this time.  But the crash is happening when trying to reuse an OOABL object.  
 

None at this time.
 

Start the appserver after adding the startup parameter -reusableObjects 0.  This disables the reusable object cache and avoids the problem.