[ https://issues.apache.org/jira/browse/TS-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon updated TS-1035: ----------------------------- Fix Version/s: (was: 3.1.3) 3.1.2 Pushed to git > EventProcessor::spawn_thread doesn't check that there is enough event threads > and segfaults > ------------------------------------------------------------------------------------------- > > Key: TS-1035 > URL: https://issues.apache.org/jira/browse/TS-1035 > Project: Traffic Server > Issue Type: Bug > Components: Core > Affects Versions: 3.0.1 > Reporter: Brian Geffon > Assignee: Brian Geffon > Fix For: 3.1.2 > > Attachments: TS1035.patch, TS1035.trunk.patch > > > The easiest way to see this bug is to use several hundred ports with accept > threads turned on. The bug exists because in I_EventProcessor.h there is a > hard coded limit of 512 event threads and there is no check in spawn_thread > that you haven't exceeded that limit so it will result in a segfault if > you're creating too many threads. From what I can tell the best solution is > an assertion that you haven't exceeded MAX_EVENT_THREADS. > Patch is included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira