[#LIBOMV-377] Bug in OpenMetaverse.NetworkManager.OutgoingPacketHandler()

libopenmetaverse

Bug in OpenMetaverse.NetworkManager.OutgoingPacketHandler()

Created: 12/Sep/08 01:11 PM Updated: 30/Sep/08 07:16 PM

Component/s:

Networking

Affects Version/s:

None

Fix Version/s:

0.6.0

Severity:	Low
Environment:	.NET / Windows32
Steps to Reproduce:	« Hide run dashboard.exe example logging in with an avatar with a large inventory, click Inventory Tab Expected: inventory folders to be shown in tree Got: Exception listed above Show » run dashboard.exe example logging in with an avatar with a large inventory, click Inventory Tab Expected: inventory folders to be shown in tree Got: Exception listed above

Description

« Hide

My avatar has 10k items in inventory and when i load my inventory list it works perfect
My partner has 30k inventory items and when it loads it throws the error

Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection.

Stack trace shows

" at System.Buffer.BlockCopy(Array src, Int32 srcOffset, Array dst, Int32 dstOffset, Int32 count)\r\n at OpenMetaverse.Simulator.SendPacketUnqueued(Packet packet, Boolean setSequence)\r\n at OpenMetaverse.NetworkManager.OutgoingPacketHandler()\r\n at System.Threading.ThreadHelper.ThreadStart_Context(Object state)\r\n at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)\r\n at System.Threading.ThreadHelper.ThreadStart()"

All

Comments

Change History

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Jim Radford added a comment - 12/Sep/08 02:37 PM

Increased BUFFER_SIZE to accomodate oversized packets to 4096, will cause additional memory to be wasted, however the Simulator is not respecting its own limits.

[ Permalink | « Hide ]

Shack Dougall added a comment - 30/Sep/08 07:26 AM

If I understand the fix, it just raises the upper limit of what inventories will work, but doesn't fix the root cause.

I have had two users who have reported details of this problem with Prim Composer. r2240 fixed the problem for one user, but the other is still having problems. However, the second person was able to get around the problem by using an alt. (http://liferain.com/downloads/forums/primcomposer-for-3ds-max/maxport-crash/)

I think the current fix is sufficient, but it would be helpful to have a more complete description of what triggers the problem. Is it the total size of the inventory that is the issue or is it the number of items in a particular folder? Is it dependent on the length of item names in inventory or solely on the number of items?

I'm asking because Prim Composer doesn't try to look at the whole inventory. It basically just looks at the contents of the root folder, so that it can find a special work folder that it uses to place some of its output. I'm looking for an accurate description of what a user would need to change about their inventory to get things working.

Thanks in advance for any insight you can provide.

[ Permalink | « Hide ]

Daten Thielt added a comment - 30/Sep/08 07:16 PM

from my observation its the total number of folders in the root of the inventory