• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SNOW-177
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Normal Normal
Assignee: Unassigned
Reporter: Maggie Darwin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
6. Second Life Snowglobe - SNOW

Crash when Vista vmem exceeds 2gig. Looks the same as VWR-8841.

Created: 08/Aug/09 01:18 PM   Updated: 13/Aug/09 04:17 PM
Return to search
Component/s: Crashes
Affects Version/s: Snowglobe 1.1
Fix Version/s: None

Environment:
Snowglobe 1.1.2 (2584) Aug 1 2009 09:40:23 (Snowglobe Release)
Release Notes

Built with MSVC version 1400

You are at 173241.1, 285679.9, 110.7 in Harrington located at sim2320.agni.lindenlab.com (216.82.17.71:13002)
Second Life Server 1.27.2.129782
Release Notes

CPU: Intel Core 2 Series Processor (2399 MHz)
Memory: 3327 MB
OS Version: Microsoft Windows Vista (Build 6000)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8800 GTS/PCI/SSE2
Windows Graphics Driver Version: 7.15.0011.8048
OpenGL Version: 2.1.2

libcurl Version: libcurl/7.19.6-CVS OpenSSL/0.9.8j c-ares/1.6.0
J2C Decoder Version: KDU
Audio Driver Version: FMOD version 3.750000
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.25966 (Mozilla GRE version 1.8.1.21_0000000000)
Packets Lost: 0/2298 (0.0%)
Issue Links:
Relates
 


 Description  « Hide
See VWR-8841

Vmem as reported by ProcExp climbs slowly to 2gb (1.3 gig private bytes), crash follows on any siginificant memory allocation thereafter, especialy media browser, map launch, profile display



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Rob Linden added a comment - 13/Aug/09 04:17 PM
Since this is already captured in VWR-8841, let's not leave this one open. We'll likely be making a switch to tcmalloc soon, which may make this moot, but can't say for sure that that is the fix.