EXT-8458 FIXED ensure that static pointer to instance of LLPanelStandStopFlying is always valid to prevent crash.

Consequences of root cause:
 Static pointer to LLPanelStandStopFlying in LLPanelStandStopFlying::getInstance() becomes invalid when the instance of the LLPanelStandStopFlying is a child of floater while it is destroying.
 Next usage of that pointed cause a crash.

Root Cause:
 1. LLFloater::closeFloater sets floater invisible and marks floater as "dead" but does not destroy it.
 2. But that instance was still in LLFloaterReg map. It is removed in LLFloater's destructor.
 3. So it was possible on low fps to get "dead" floater with LLFloaterReg, LLFloaterMove in this case.
 4. Then LLMortician deleted floater instance shown on previous step.
    Call of setVisible(false) from the LLFloater's destructor does not call overridden LLFloaterMove's method (which is expected behavior.)
    So, child panel LLPanelStandStopFlying was not re-parented to Main View and was destroyed with LLFloaterMove.
    That leaded to the "Top Reason" described above.

FIX:
1. Ensure that LLPanelStandStopFlying is not a child of LLFloaterMove on its destroying.
2. Synchronized removing of a floater instance from the LLFloaterReg when it is marked as "dead".

Note: both changes fixes this bug independently, but I included both of them into result patch to avoid similar but in the future.

Reviewed by Vadim Savchuk at https://codereview.productengine.com/secondlife/r/781/

--HG--
branch : product-engine

1 files changed, 10 insertions, 0 deletions

diff --git a/indra/newview/llmoveview.cpp b/indra/newview/llmoveview.cpp
index 6ae4a5e5e4..fc41137686 100644
--- a/indra/newview/llmoveview.cpp
+++ b/indra/newview/llmoveview.cpp
@@ -83,6 +83,16 @@ LLFloaterMove::LLFloaterMove(const LLSD& key)
 {
 }
 
+LLFloaterMove::~LLFloaterMove()
+{
+	// Ensure LLPanelStandStopFlying panel is not among floater's children. See EXT-8458.
+	setVisible(FALSE);
+
+	// Otherwise it can be destroyed and static pointer in LLPanelStandStopFlying::getInstance() will become invalid.
+	// Such situation was possible when LLFloaterReg returns "dead" instance of floater.
+	// Should not happen after LLFloater::destroy was modified to remove "dead" instances from LLFloaterReg.
+}
+
 // virtual
 BOOL LLFloaterMove::postBuild()
 {