Skip to content
This repository was archived by the owner on Apr 4, 2025. It is now read-only.

[BUG-41029] [Project Alex Ivy] Viewer memory use is reported incorrectly once memory use goes over ~ 4GB #12623

Open
sl-service-account opened this issue Dec 10, 2016 · 0 comments

Comments

@sl-service-account
Copy link

Steps to Reproduce

  • Login on the 64bit Project Alex Ivy viewer.
    Develop -> Show Info -> Show Memory.

  • Get the viewer memory over 4-5 GB.

  • See "Other Information" for how to quickly get memory high.

  • Observe the memory readings bottom right of the screen and in the session log.

  • Set debug setting MemoryLogFrequency to 5.0 so you can see memory printed to the log every 5 seconds (default is every 600 secs).

    Observed Behaviour

  • When the viewer uses more then ~4-5 GB of memory, the memory readings will be incorrect in screen console (Show Info -> Show Memory) and in the session log.

  • I'm unsure of the exact memory amount where the bug starts to reproduce.

  • The correct memory use reading will display in Windows task manager.

  • For example, Show Info -> Show memory and viewer log reports memory use as 0.98GB when actual memory use is 5.08GB.

    Expected Behaviour

  • Memory readings on screen console and session log should be accurate.

  • Bug does not reproduce on 32bit release, Second Life 5.0.0.321958 (Second Life Release), but only because you cannot get memory use high enough to reproduce the bug without crashing from out of memory on a 32bit viewer :)

    Other Information

    Some ways to quickly get memory use over 4 GB.

    1. Login on an account with a huge inventory
      Open inventory floater.
      Under the gear menu (Show additional options), choose "New Inventory window".
      Each time a new secondary inventory window is opened, memory use will increase. If the account has a large inventory, it will increase by a lot.
      Keep opening new secondary inventory windows till memory use gets high enough to repro.
      You can close each secondary inventory window once it's opened, that extra memory is never freed up (yuk!).

    2. Set draw distance to max, RenderVolumeLODFactor to 4.
      Teleport to a location that's very busy & texture rich, with lots of avatars.
      Cam around a lot.

    3. Wear or rez the [QA version] Black Alchemista Hackeo a Finisher e a power object.
      Kyle Linden can provide this object.
      For each copy of this object the viewer renders, memory use will increase by >1GB.

Original Jira Fields
Field Value
Issue BUG-41029
Summary [Project Alex Ivy] Viewer memory use is reported incorrectly once memory use goes over ~ 4GB
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Reporter Whirly Fizzle (whirly.fizzle)
Created at 2016-12-10T20:59:17Z
Updated at 2016-12-12T17:44:47Z
{
  'Business Unit': ['Platform'],
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Filling in...',
  'What were you doing when it happened?': '....',
  'What were you expecting to happen instead?': '....',
}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant