Segfaults in glibc malloc should be reported to glibc developers. Not here. There’s nothing we can do about it other than to suggest Solaris for high performance modperl shops.
On Fri, Aug 19, 2022 at 9:28 PM Joe Schaefer <j...@sunstarsys.com> wrote: > My pleasure. Nobody’s going to fix this from the modperl developer side. > We don’t care any more. That ship sailed 20 years ago. I don’t think it’s > ever not worked on Solaris, so you get what you pay for in the end. > > On Fri, Aug 19, 2022 at 9:25 PM Edward J. Sabol <edwardjsa...@gmail.com> > wrote: > >> Very interesting, Joe! Thank you for sharing your insights into this and >> experience with it. Here’s hoping someone can solve/fix the problem with >> mod_perl threads on Linux. >> >> Regards, >> Ed >> >> On Aug 19, 2022, at 1:44 PM, j...@sunstarsys.com wrote: >> > The problem is really confined to embedded uses of ithreads, because >> Perl itself will mutex-wrap the malloc calls. In httpd, so do all >> apr_pool_t calls to malloc. It's when the two memory management techniques >> are interacting that there is no application-level way to guard against >> thread contention in libc's malloc. >> > >> > Mod_perl+ithreads are awesome, when used intelligently. You gain >> intelligence from experience trying to use it in a lot of ways that suck, >> until you hit one the path that yields success. >> > -- > Joe Schaefer, Ph.D. > We only build what you need built. > <j...@sunstarsys.com> > 954.253.3732 <//954.253.3732> > > > -- Joe Schaefer, Ph.D. We only build what you need built. <j...@sunstarsys.com> 954.253.3732 <//954.253.3732>
