error on logging out

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Log in
2.Log out

What is the expected output? What do you see instead?
Expected to just be logged out..logged out with error message

Please use labels and text to provide additional information.
TypeError: Error #1009: Cannot access a property or method of a null object 
reference.
    at org.bigbluebutton.modules.whiteboard.views::WhiteboardToolbar/setPositionAndDepth()[/var/lib/hudson/jobs/bbb-client/workspace/src/org/bigbluebutton/modules/whiteboard/views/WhiteboardToolbar.mxml:267]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.core::UIComponent/dispatchEvent()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:13128]
    at mx.core::UIComponent/dispatchMoveEvent()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:10178]
    at mx.core::UIComponent/move()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:9655]
    at mx.effects.effectClasses::MoveInstance/onTweenUpdate()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\effectClasses\MoveInstance.as:416]
    at mx.effects.effectClasses::TweenEffectInstance/onTweenEnd()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\effectClasses\TweenEffectInstance.as:425]
    at mx.effects.effectClasses::MoveInstance/onTweenEnd()[E:\dev\hero_private\frameworks\projects\framework\src\mx\effects\effectClasses\MoveInstance.as:463]
    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()

Original issue reported on code.google.com by mohamed....@gmail.com on 15 Oct 2013 at 3:29

[GoogleCodeExporter]

I'm getting a different error on logout.

Error: Error #2014: Feature is not available at this time.
    at flash.accessibility::Accessibility$/updateProperties()
    at mx.accessibility::AlertAccImpl/eventHandler()[E:\dev\hero_private\frameworks\projects\mx\src\mx\accessibility\AlertAccImpl.as:204]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.core::UIComponent/dispatchEvent()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:13128]
    at mx.core::UIComponent/set initialized()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:1818]
    at mx.managers::LayoutManager/validateClient()[E:\dev\hero_private\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1090]
    at mx.core::UIComponent/validateNow()[E:\dev\hero_private\frameworks\projects\framework\src\mx\core\UIComponent.as:8067]
    at org.bigbluebutton.main.views::MainToolbar/confirmLogout()[/var/lib/hudson/jobs/bbb-client/workspace/src/org/bigbluebutton/main/views/MainToolbar.mxml:185]
    at org.bigbluebutton.main.views::MainToolbar/__btnLogout_click()[/var/lib/hudson/jobs/bbb-client/workspace/src/org/bigbluebutton/main/views/MainToolbar.mxml:353]

Since the user is logging out, if their client throws an error it's not going 
to affect anything (they are logging out), but it's worth while looking closer 
to ensure it's not a symptom of a larger issue.

Original comment by ffdixon@gmail.com on 19 Oct 2013 at 9:29

• Added labels: Component-Client, Priority-Low, Stability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I think Mohamed's error is just a race condition with window destruction.
The whiteboard toolbar needs to know the positioning of the presentation
window and if the window is destroyed first it will throw and error. We
could put a check for null at the start of the method, but it's a pretty
fringe case.

Your error Fred is different because that whole stack trace is all
framework methods that we don't touch. I'm not really sure what the issue
could be other then maybe a fluke. It would be a good idea to keep watching
for it happening again though.

Original comment by capil...@gmail.com on 20 Oct 2013 at 7:08