Cliff, Many many thanks for your feedback (and your patch).
This is very very interesting. I also get segfault a few hours after an intentional restart I also get memory leaks (or at least memory is increasing but that may be because I have bigger and bigger arrays on my own code, don't know). I also noticed that crashes usually happen in the night around 5-6 am (supposedly caused by remote American users, I am hosted in Europe). Your patch really sounds interesting, but I am stuck with the Mysql problem. Probably this is not much to fix from the authors of APE, but as we all know they are now very active these days. As I am working on a version 2 of my platform and getting closer and closer to release, I don't really see myself spending time on working around the Mysql issue as others did (calling PHP pages). This might generate unexepected surprises so I don't really want to take the risk of putting something really new like this into my version 2. Looks like I am stuck... Thanks again for your precious help. At least, now, I most likely know what is going on. 2012/12/31 Cliff <[email protected]> > Two questions: >> >> 1) I have looked for ape_disconnect() in the source code of APE but could >> not find it? Where is it? >> >> In the source file servers.c >> >> 2) I ran into this description of the last modifications made to APE in >> Github "Fix stuck subuser when previous subuser was still writing data. >> Also make socket write buffer size a multiple of 2K." >> I could not find any other information here. Can someone point out why >> this patch was made exactly and whether it is advisable for me to download >> latest code and compile it (with MYSQL which may or may not work) >> >> > I believe this is my patch. I had several users that were halfway around > the world from my servers and on very low bandwidth internet connections > that were routinely causing APEServer segfault crashes. There were several > different crash scenarios and some cases that only resulted in memory > leakage, but I do recall that I would often experience a segfault crash > soon after an intentional APEServer restart. It sounds like you might > benefit from this patch. I do not use MYSQL so I cannot comment on that. > I did encounter problems with the recompiled latest libape-spidermonkey > that I never did resolve since I found that the 1.1.1 release version works > fine for me. > > Since these patches my APEServer has been running for 2 months now with no > segfaults and no noticable memory leakage. > > Regards, > Cliff Atwood > > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ > -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
