A common cause is a READ, WRITE or DELETE of an O/S level text file in BASIC. Import/export programs and an unexpectedly large file?
Regards JayJay -----Original Message----- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: 06 May 2009 17:49 To: u2-users@listserver.u2ug.org Subject: Re: [U2] U_shmalloc() failed Symeon: Here's some malloc information in the troubleshooting guide: Error on malloc a space (size=xxx), errno=xxx Memory allocation error. The requested size is too large. You have run out of room in the data space of a process. One solution is to install more physical memory. You may also need more swap space. Swap space must be at least as large as physical memory. Or, if you have linked in C routines with udt, check for errors in these routines first. HTH, Bill ______________________________________________________________________ From: Symeon Breen <syme...@gmail.com> Sent: 5/6/2009 2:11 AM To: u2-users@listserver.u2ug.org Subject: [U2] U_shmalloc() failed Hi - I have a process that runs overnight that quite often crashes with this error. This is on udt7.2 on RHEL ES 4 64bit My first thought was an item/variable with more that 32Meg of data in it but i really cannot see that happening, I may be wrong on that tho ... Does anyone know why i get this error and if i should be looking toward my udtconf or the code and variable sizes. Cheers Symeon. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
