Remove a noisy debug message from bridging code.
authorMark Michelson <mmichelson@digium.com>
Mon, 21 Oct 2013 21:06:41 +0000 (21:06 +0000)
committerMark Michelson <mmichelson@digium.com>
Mon, 21 Oct 2013 21:06:41 +0000 (21:06 +0000)
This particular debug message, during a stress test, was logged so
often that it appeared that there may be a memory leak in the logger
code. In actuality, there was no memory leak, but the logger thread
was having a hard time keeping up with the demands of the rest of the
system.

Since this debug message has no value at all, the best way to fix the
problem was to just remove the message.

(closes issue AST-1225)
reported by John Bigelow

Patches:
spammy_log.diff uploaded by Mark Michelson (License #5049)
........

Merged revisions 401364 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@401365 65c4cc65-6c06-0410-ace0-fbb531ad65f3

main/bridge_channel.c

index 2917e83..f827738 100644 (file)
@@ -1879,9 +1879,6 @@ static void bridge_channel_wait(struct ast_bridge_channel *bridge_channel)
                        ast_channel_name(bridge_channel->chan));
                ast_cond_wait(&bridge_channel->cond, ao2_object_get_lockaddr(bridge_channel));
        } else {
                        ast_channel_name(bridge_channel->chan));
                ast_cond_wait(&bridge_channel->cond, ao2_object_get_lockaddr(bridge_channel));
        } else {
-               ast_debug(10, "Bridge %s: %p(%s) is going into a waitfor\n",
-                       bridge_channel->bridge->uniqueid, bridge_channel,
-                       ast_channel_name(bridge_channel->chan));
                ast_bridge_channel_unlock(bridge_channel);
                outfd = -1;
                ms = bridge_channel_next_interval(bridge_channel);
                ast_bridge_channel_unlock(bridge_channel);
                outfd = -1;
                ms = bridge_channel_next_interval(bridge_channel);