we updated our bridge on monday and have started seeing some crazy cpu
usage, even with no clients connected to a call. was able to do some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2 people join call
1, 2 people join call 2. then had everyone leave (i don't think those are
necessarily the specific repro steps, but in this case were enough to cause
the problem). even after they left, cpu usage on the bridge was very high.
in the background of the screenshot is the /colibri/stats page to show we
don't have any streams active at the time.

we updated our bridge on monday and have started seeing some crazy cpu
usage, even with no clients connected to a call. was able to do some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2 people join
call 1, 2 people join call 2. then had everyone leave (i don't think
those are necessarily the specific repro steps, but in this case were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can you look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some crazy cpu
usage, even with no clients connected to a call. was able to do some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2 people join
call 1, 2 people join call 2. then had everyone leave (i don't think
those are necessarily the specific repro steps, but in this case were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can you
look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

ah great, ok that makes sense. turns out i copied the wrong revision and i
believe 1f7982aa22d66916856e6dfed1a68fb81490641b is the oldest i found with
the problem (which corresponds to a jitsi meet update to 145, so that lines
up with what you said there). thanks for the quick update...will probably
just verify once the videobridge pom gets pushed.

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to
do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this
case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?

ah great, ok that makes sense. turns out i copied the wrong revision and i believe 1f7982aa22d66916856e6dfed1a68fb81490641b is the oldest i found with the problem (which corresponds to a jitsi meet update to 145, so that lines up with what you said there). thanks for the quick update...will probably just verify once the videobridge pom gets pushed.

we updated our bridge on monday and have started seeing some
crazy cpu
usage, even with no clients connected to a call. was able to do
some
profiling, attached the screenshots.

what i did was spin up a bridge (tip of master) and have 2
people join
call 1, 2 people join call 2. then had everyone leave (i don't
think
those are necessarily the specific repro steps, but in this case
were
enough to cause the problem).

Scary stuff! I think I made this possible with this one[0], but can
you look through your logs for an exception, so we can confirm?