secondlife / secondlife/viewer
Avoid reading the same XML file multiple times
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Any version of SecondLife viewer
Description
Some XML files are being read very often, multiple times per session
For chat messages:
indra\newview\skins\default\xui\en\panel_chat_header.xml
indra\newview\skins\default\xui\en\inspector_info_ctrl.xml
indra\newview\skins\default\xui\en\panel_chat_separator.xml
For notifications:
indra\newview\skins\default\xui\en\favorites_bar_button.xml
indra\newview\skins\default\xui\en\panel_notification.xml
indra\newview\skins\default\xui\en\panel_toast.xml
And maybe some other files, needs investigate
Reproduction steps
- Create file
logcontrol-dev.xmlin the folderC:\Users\user\AppData\Roaming\SecondLife\user_settings
with the following contents:
<llsd>
<map>
<key>default-level</key>
<string>ERROR</string>
<key>print-location</key>
<boolean>false</boolean>
<key>settings</key>
<array>
<map>
<key>level</key>
<string>DEBUG</string>
<key>functions</key>
<array>
<string>parseFile</string>
</array>
</map>
</array>
</map>
</llsd>
-
Start SL viewer, open chat floater, view notifications and so on
-
Close viewer
-
Read the file
C:\Users\user\AppData\Roaming\SecondLife\logs\SecondLife.log -
Verify repeated readings of the same XML files
Links
Is integrated into
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with logcontrol-dev.xml and inspect SecondLife.log for repeated parseFile entries. Trace the listed chat and notification XML files under indra/newview/skins/default/xui/en, then determine the relevant loading paths. Done means the same XML resources are no longer read repeatedly during a viewer session and the behavior is verified in the log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100