Hi Sven, > The following error happened in a normal web server (no https), > unfortunately such errors cannot be reproduced because they > are caused by incorrect clients: I'm not quite sure what you mean by "incorrect clients" however...
> *** ERROR:string->obj: > > > Corrupted string at index 373852804864238536/188 -- > (%01%13%3A%22%01%0AsalutationF%3A%22%01%0Afirst-nameF%3A%22%01%09last-nameF%3A%22%01%07companyF%3A%22%01%07addressF%3A%22%01%05emailF%3A%22%01%05phoneF%3A%22%01%06clientF%3A%22%01%04urlsF. > 1. &pool-scheduler3285, > GC Warning: Failed to expand heap by -2088685568 bytes > GC Warning: Failed to expand heap by -2122240000 bytes > > The string index shown is much too large and leads to > a problematic allocation request. I have improved the serialization corruption detection. Such errors should now be handled smoothly. The patch will be found in the next Bigloo 4.3b alpha version. Cheers, -- Manuel
