Closed GoogleCodeExporter closed 9 years ago
I have a server that is running an older version of BBB (build 4283-2013-07-15)
and I can't reproduce the issue on that server so it seems like the issue arose
at some point between then and now.
Original comment by capil...@gmail.com
on 15 Nov 2013 at 10:06
I have finally narrowed down down the cause to three commits.
https://github.com/bigbluebutton/bigbluebutton/compare/c350b6c...d1ee41a . Two
of the commits are related to ruby recording files and are inconsequential, but
somewhere in one (or more) of the three other commits is the cause of the CPU
spike. I've looked through the diffs and I can't see anything that sticks out,
but it's there somewhere.
Original comment by capil...@gmail.com
on 8 Jan 2014 at 9:45
I'm still not sure what is causing this and the effect of the bug isn't always
the same. Sometimes it locks up, sometimes it crashes, sometimes it's just
slow. I installed the latest debug version of Flash (12.0.x) and I got an error
log that might prove useful.
Error #1502: A script has executed for longer than the default timeout period
of 15 seconds.
at mx.core::UIComponent/processEffectFinished()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:11840]
at mx.core::UIComponent/updateCompleteHandler()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:11812]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\hero_private\frameworks\projects\framework\src\mx\managers\LayoutManager.as:851]
at mx.managers::LayoutManager/validateNow()[E:\dev\hero_private\frameworks\projects\framework\src\mx\managers\LayoutManager.as:878]
at mx.effects.effectClasses::TweenEffectInstance/onTweenEnd()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\effectClasses\TweenEffectInstance.as:430]
at mx.effects.effectClasses::ResizeInstance/onTweenEnd()[E:\dev\hero_private\frameworks\projects\mx\src\mx\effects\effectClasses\ResizeInstance.as:495]
at mx.effects::Tween/endTween()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\Tween.as:566]
at mx.effects::Tween/http://www.adobe.com/2006/flex/mx/internal::doInterval()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\Tween.as:607]
at mx.effects::Tween$/timerHandler()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\Tween.as:191]
at flash.utils::Timer/_timerDispatch()
at flash.utils::Timer/tick()
It looks like Flash is getting stuck in an animation and after 15s it cuts and
then continues execution.
Original comment by capil...@gmail.com
on 16 Jan 2014 at 6:07
Original comment by ffdixon@gmail.com
on 3 Feb 2014 at 10:50
Original comment by ritza...@gmail.com
on 25 Jul 2014 at 2:39
Issue 1782 has been merged into this issue.
Original comment by ghazi.no...@gmail.com
on 14 Aug 2014 at 8:32
What version flexlib library is bbb using ? is it a custom build ?
Original comment by ghazi.no...@gmail.com
on 14 Aug 2014 at 8:32
It's a build of the latest with some customizations.
Original comment by capil...@gmail.com
on 14 Aug 2014 at 12:14
Original comment by ffdixon@gmail.com
on 24 Aug 2014 at 12:29
Can you confirm that we can't reproduce this issue any more ?
Original comment by ghazi.no...@gmail.com
on 25 Aug 2014 at 10:19
I can reproduce it on my laptop so it is definitely still present. Windows 7,
Chrome 36, dev.bigbluebutton.org
Original comment by capil...@gmail.com
on 25 Aug 2014 at 6:16
I cannot reproduce it when enabling Flash Player remote debug. But in Flash
Player normal mode we can see it.
Original comment by ghazi.no...@gmail.com
on 26 Aug 2014 at 8:58
The issue caused by the Flex SDK.
I have created a fix under this branch :
https://github.com/speakserve/bigbluebutton/compare/fix-window-maximize-lockup?e
xpand=1
I have tested it successfully. Please test it well before merging it.
Original comment by ghazi.no...@gmail.com
on 26 Aug 2014 at 9:30
Original comment by ghazi.no...@gmail.com
on 28 Aug 2014 at 2:24
Original issue reported on code.google.com by
capil...@gmail.com
on 14 Nov 2013 at 6:56