| Summary: | ASTERISK-22210: 'Bad Magic Number' with 160 Confbridge or more. | ||
| Reporter: | Fabian Andrey Garzón Niño (monse40) | Labels: | |
| Date Opened: | 2013-07-29 19:04:07 | Date Closed: | 2013-07-29 20:05:11 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Bridges/bridge_simple |
| Versions: | 11.3.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Asterisk Server Receiving calls from another Asterisk Server(Stress Server) , Dialplan with Bridge Application. | Attachments: | |
| Description: | We are trying to measure the Bridge Application Improve with a stress test, but when the Bridges number is close to 160 the application shows the 'Bad magin Number' error.
we have been investigated but have not found anything. Thanks in advance! | ||
| Comments: | By: Matt Jordan (mjordan) 2013-07-29 20:05:11.828-0500 First, this is not a support forum. Posting a reference to a memory address being passed to an ao2 routine that is not a valid allocated ao2 object (which is the 'bad magic number error') isn't something that anyone can help with if you haven't performed basic reference count debugging. The Asterisk wiki has information on how to go about [getting a reference count debug log|https://wiki.asterisk.org/wiki/display/AST/Reference+Count+Debugging]. Second, as with anything, if you push it hard enough on some given machine, it may eventually topple (for some specific definition of "push" and "machine"). The fact that you over-taxed a particular system and caused it to respond poorly is not, in and of itself, a bug. If you want to discuss your stress testing further, the asterisk-dev list may be an appropriate place to discuss your findings. Finally, please note that the [instructions for filing bugs|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] are rather clear on what is needed for filing issues. In the future, please follow the guidelines when filing bug reports. Thanks! | ||