summaryrefslogtreecommitdiff
path: root/indra/newview/llnotificationalerthandler.cpp
diff options
context:
space:
mode:
authorRoxie Linden <roxie@lindenlab.com>2011-07-15 12:53:09 -0700
committerRoxie Linden <roxie@lindenlab.com>2011-07-15 12:53:09 -0700
commitb88c7166f4323d9035bc78f517ff51396e80c123 (patch)
treeee6bcdccf20be9d40a7966883122ecb369001b89 /indra/newview/llnotificationalerthandler.cpp
parent873ba5178fceb0b96f94d1725586950e7f1be8d9 (diff)
STORM-1355 Memory issues from UI for very large groups
This change is not guaranteed to fix this issue as the issue is difficult to repro, but there was a sketchy case group member responses come back from the simulator in message packets. For very large numbers of members, there may be a large number of packets received. The member data is placed in a structure of type LLGroupMgrGroupData, based on the group id. The problem is, if the user refreshes the group before the entire contents of the previous request comes back, response packets from the previous request will be intermingled with the responses from the refresh. Both the request call and the response handler would create the group data structure, if the structure wasn't already there. There may be a case where a response from the previous request causes creation of the group data, populating it with the contents of the response, and the responses from the second request would use that group data structure. Also, cleaned up some comments and variable names to be consistent
Diffstat (limited to 'indra/newview/llnotificationalerthandler.cpp')
0 files changed, 0 insertions, 0 deletions