Jump to content

Ananda Sandgrain

Resident
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ananda Sandgrain

  • Rank
    Newbie
  1. I'm not asking for help solving "my crashing issues." The issues are well known, they are thoroughly documented elsewhere. What I haven't been able to find anywhere, though, is information about why certain things are done the way they are. Why is so much information loaded into memory. What purpose does it serve. Why is it not able to be offloaded onto the hard drive cache when it's not being used (which is 99% percent of the time). Tu savais?
  2. There is an ongoing set of issues about the memory leaks in jira, yes. Most of them have been there, been serious, and been unresolved for a year or more. But I am trying to find out about something that doesn't necessarily qualify as a bug, which is to find out why exactly my inventory consumes over half a gigabyte of memory within a minute of logging into the world. The presense or absence of a loaded inventory is the number one factor in whether the memory leaks take 20 minutes or several hours to get me an out-of-memory crash. @ Madeleine, Dora - yes the cache holds your inventory file
  3. Yep, currently I'm still using a 32-bit OS, so I'm out of luck. Apparently the inventory load does average about 7-8 kilobytes per item, which just boggles the mind. So what happens is, the memory leaks will balloon things out over the course of a few hours, but there's only so much room to play with. Without the inventory load, I've got something like 900 megabytes to spare, but once it loads there's only 250 megabytes left, and the memory leaks just chew through that way too fast.
  4. Interesting. I haven't actually tested it out with a low-inventory account. In that case what would be nice to find out is what exactly *is* SL loading into memory during those initial minutes that clog things up so badly. It has something to do with inventory loading, because what I find is that I will consistently crash every 20-30 minutes if it is loaded, but if for some reason my inventory fails to load again after a cache clear, it will run fine for hours. I kind of need that memory space back and it is clearly nonessential to actually running the program, so it would be nice to find
  5. I've been experiencing out-of-memory related crashes with viewers ever since the advent of the mesh versions. Eventually I got around to discovering something odd - by far the largest chunk of my computer's memory is being used up by the Inventory when I first load up a viewer. If I clear cache first, it typically uses about 350,000 K of memory. But if my whole inventory has loaded, it will start off with 950,000 K. Now, having been around for 8 years, my inventory has grown to be a huge mess, I "only" have 77,000 items in it. But what I can't understand is why SL feels the need
  6. Ah, thank you, yes. I quite naturally and sensibly disabled the SL viewer from accepting javascript and cookies, and redirect to my usual browser anyways. So naturally I never picked up on the fact that Search and now Web Profiles are ignoring my suggestions. And it looks like you answered the question on why they force-downloaded this program on me, apparently they snuck this in as an "option" in preferences and left it on automatic by default. There's a lot of bad and untrustworthy behavior floating around here. I might have to reevaluate my "no-second chances" stance on the third part
  7. Can you address a number of things? 1. Why is this out of beta? Moreover, why, as a 2.4 user, was this just FORCE installed on my system? 2. The web profiles are not functional. They don't contain Picks, they don't let me edit anything, and since there are no Picks, I can no longer use this as a workaround for the broken Search function. 3. Why is the authorization token on search still permanently broken? Meh, I guess it's back to the third party viewers if I want to actuall do anything in SL.
×
×
  • Create New...