Summary: | ASTERISK-09079: [patch] Improper locking in meetme results in a segfault | ||
Reporter: | Clod Patry (junky) | Labels: | |
Date Opened: | 2007-03-22 21:34:35 | Date Closed: | 2007-07-11 19:59:11 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_meetme |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) meetme_crash.txt ( 1) meetme.txt | |
Description: | With heavy volume, i'm getting that crash, like once/10 days. For unknown reason at this stage, it's like user is NULL when doing a meetme list foo. ****** ADDITIONAL INFORMATION ****** there's a call to time(&user->jointime) then we insert the user at the tail of conflist. See around line 1348. | ||
Comments: | By: Clod Patry (junky) 2007-03-23 00:20:01 attachment is just a hack, since it doesnt resolve the real problem (a user is NULL). That might be helpful for other users. By: Clod Patry (junky) 2007-03-23 01:40:33 Maybe we could apply that patch until we find where the real problem is. Im up for finding/testing to track down the source of the problem too. By: Clod Patry (junky) 2007-06-05 17:08:40 any chance we can get meetme_crash.txt commited to 1.4? cause I've to patch manually all my install. That patch is running fine on a production server for over 2 months now. By: Russell Bryant (russell) 2007-06-05 18:02:05 This issue has been resolved in 1.4 and trunk in revisions 67558 and 67560. Thanks! |