Hello, Is there a way to handle the exceptions (access violation, heap corruption etc) thrown by an output filter module within the module itself so that it does not propagate till the httpd.exe server resulting in a server crash?
The C++ output filter module that I have written makes use of native memory allocation methods like malloc/new in some cases. I have not used the APR request pool here since the allocations in these methods are very much short lived and are called many times within a single request. So rather than waiting for the request completion and then the pool manager releasing this memory, I'm using native new/delete calls to do the allocation/deallocation so that I can release the memory immediately after use. The issue is, in some rare case scenarios I saw a httpd.exe crash that was due to heap corruption and access violation during new/delete calls in these methods. Is there a way I can gracefully handle these within the module by catching such exceptions and trying to handle them, rather that propagating this exception resulting in httpd.exe crash? Worst case even if no filtering happened due to a crash in the module, I'd prefer that the filter sent back the original data (that was passed to the filter when the filter callback was made by the server) down the filter chain, ofcourse after logging this information for later troubleshooting. Thankyou.
