[sldev] Volunteer needed!

Bridie Saccocio bridie at lindenlab.com
Thu Jun 14 17:58:43 PDT 2007


Hey there-

Good news -- many resolved PJIRA issues that went out with 1.17 this  
week!  So - we're looking for a little clean-up help w/PJIRA...

Would anyone be willing to volunteer to go through the following  
PJIRA issues marked as "Fixed Internally" and do the following:
1.) Re-open the issue
2.) Resolve the issue as "Fixed"
3.) Add a comment "Fixed in 1.17.0(112)"

* VWR-1040: crash when opening several gestures quickly
* VWR-966: Minor memory leak in llfloaterpreferences.cpp and a tiny  
leak in llstatup.cpp
* VWR-908: Various memory leaks in the group dialog
* VWR-871: More bad f00d: Two minor (or inconsequential) misses of  
initializing object members
* VWR-870: Memory violation through uninitialized variable (invisible  
or unrendered flexis)
* VWR-869: Possible hard-loop (endless, viewer-hang) in script editor
* VWR-827: Toruses are borked after making/editing sculpted prims
* VWR-823: Two unintialized variables in lltexturefetch.cpp
* VWR-822: “Create new…” clothing buttons don’t auto-wear items
* VWR-810: Destructor forgets to delete mFloaterContros member in  
llui/llview.cpp
* VWR-809: Destructor fails to clean up global menus in llviewermenu.cpp
* VWR-808: Incorrect cleanup in message.cpp
* VWR-807: Forgets to delete gToolInspect in lltoolmgr.cpp
* VWR-804: Quirk in llviewerwindow.cpp
* VWR-805: LLCurl not properly cleaned up
* VWR-765: Cannot open embedded notecards in other notecards when  
Automatic preview of new notecards/textures/landmarks is off
* VWR-409: New Feature -> UI -> Dialog -> Buy Copy/Contents ->  
Default Action -> Cancel
* VWR-682: Text Editors should try to preserve X cursor position
* VWR-671: Line editor history for recalling previously typed lines
* VWR-648: Texture picker should highlight the texture in the swatch
* VWR-412: Object editing arrows hidden but clickable on objects you  
can’t edit.
* VWR-364: Viewer memory leak

Ideally, the reported will notice the change and regress the issue --  
but if you'd like to do that too, it would be most appreciated!

Thanks!

--Bridie


More information about the SLDev mailing list