Wednesday, November 26, 2008

Current Debug Compiles (Windows)?

I have a question to the fellow (Windows) developers. I tried an 1.21. compile recently but for my favorite game for rainy Sundays I need a debug compile (real Debug, not ReleaseWithDebug). The Debug compile failed somewhere in the boost library headers with an obscure error message (the way boost is working with templates I guess every error message is obscure). I didn't want to dig into it so I gave up pretty quickly.

So here's my question: Can anyone build a Debug version on the out-of-the box sources of the more recent official viewers? If so, which version?

Also (question to everyone): What's the current state of official viewers in regards to memory leaks?

Well, before you get too excited, I don't plan to make a new viewer, but if I'd find something interesting, I'd sure share it with my fellow developers.


Nick

26 comments:

zatzai.com said...

The biggest change for me has been the new Nvidia drivers. I was getting several crashes prior but since then it's rare that I crash. I've also been running mostly with advanced shaders off as I noticed memory leak woes with them on. The problem mostly went away with it off (Basic shaders are still on). However I've been running fine with full shaders on the new Nvidia drivers... but I have only been doing so for a short time so I'm not sure yet how stable that is.

Henri Beauchamp said...

Greetings, Nicholaz ! :-)

I don't do Windoze builds, but you might find interesting info on boost problems on the SL Wiki:
https://wiki.secondlife.com/wiki/User:Michelle2_Zenovka/cmake#boost_hell

As for the memory leaks in v1.2x viewers, they are horrible and probably the reason of many slow downs and freezes. In Linux, I start at less than 400Mb of memory used by the viewer when starting it up and when frequenting crowded places, I end up at over 2.5Gb of memory used by the viewer before I must relog because of freezes or slow downs (and that's with the Cool SL Viewer which already plugs some of the official viewers' memory leaks).

So, there is indeed a LOT of room for improvements in v1.2x viewers...

Latif Khalifa said...

Hi Nicholaz,

I am currently playing with 1.22 branch, which is in Release Candidate mode now (RC1). Lindens have switch their official build environment to VS 2005 for this one, and I am using cmake + VS 2005 with it. I have no problems building any configuration with these tools, including Debug.

Latif Khalifa said...

Btw. I forgot to mention that problems with the boost libraries are related to using VS 2008 to build. No problems with now "official" VS 2005 tool chain.

Nicholaz "The Mad Patcher" Beresford said...

Thanks Latif for testing.

I was doing Cmake with 2005 (our primary compiler anyway) and 1.21.6. Will try with 1.22.


@Henry: I'll have a look. As long as they don't lose the memory in the GL stuff (forgetting textures) I'm sure I can dig up something.

Nicholaz "The Mad Patcher" Beresford said...

@zatzai: that sounds a bit like graphics issues which is beyond my area of expertise, but if not, and if I can get the damn thing to compile, we'll see what else is there.

Boy Lane said...

I haven't touched 1.22 yet. So I can't comment on any issues to compile under Windows. In the moment I'm a bit tired of all and RL takes its toll.

Boy

Tharkis said...

I agree, the latest "official" viewers blow goats. I've been using a build of Boy's to do any scripting work. And the last Nicholaz BE version for when I am actually in SL for anything else.

The official viewer is way out of control with regards to memory leaks. I hope you get a Nicholaz version out soon.

Thanks,
Tharkis

Boy Lane said...

I just tried a debug build of the 1.22.1 RC and it worked without problems using VS2005.

Nicholaz "The Mad Patcher" Beresford said...

I can a debug build now also, but it doesn't run.

Can you guys actually start the debug-viewer?


Nick

Alexandra Rucker said...

Well, before you get too excited, I don't plan to make a new viewer

Teh lab may not appreciate it, but that's their problem. The rest of us rank-n-file users really DO appreciate your work.

I know you're not planning on a new viewer, but if you do, there will be a LOT of happy happy ECSTATIC users. :)

The memory leaks in the current release viewer are absolutely INSANE.

Nicholaz "The Mad Patcher" Beresford said...

I've got the L. version compiled and ran it for an hour or two. It didn't show any tremendous leaks though (and once crashed after 45 minutes).

What exactly are you doing to make it grow?

I mostly stayed in busy places and teleported a bit when all textures have settled down, but the memory usage in the taskmanager (Windows) was somewhat higher than my versions, but never seemed to be growing infinitely. (My viewers show about 300-500MB memory consumption after some time, the Linden viewer was about 450-650 but never got beyond 700).

Nick

Nicholaz "The Mad Patcher" Beresford said...

(It may be, as Zazai says, a driver issue, depending on which video board is used, I have an oldish Nvidia 7600GS).

Henri Beauchamp said...

@Nicholaz

You should not need to do anything special to get the memory leaks. Just hanging out in a night club or other crowded place should do.

I'm indeed using the latest NVIDIA drivers (tried both the release and beta drivers), on a 8800GT, but under Linux.

Also, all the shaders are turned on and all graphic settings maxed out (except draw distance which is set to 128m and the Sky details set to Low).

The hardware settings are:
Anisotropic filtering on.
Antialiasing on (4x)
VBO on

Tillie Ariantho said...

I do fashion show photos at 1680x1050 resolution and maximum display settings, and after a lot snappshotting and zooming around the client gets slower and slower and eats up memory until it crashes. I dont need to TP, I relog right at the catwalk and stay there all the time... I have 3,something GB memory (whatever 32bit XP SP3 gives me from 4GB) and an nvidia card (gtx 260) with 896 MB RAM

maybe that helps. ^^

Anonymous said...

i am having a huge problem with a dns error i cant get into my sl and i cannot figure out how to dl the nicholaz viewer can some one help me ... my sn is twysted demonia inworld and wilydchilyd on the big y... thanks for any help you can give me in advance

Caliah Lyon said...

Hello Nicholaz,

I've been using your viewers for a very long time now and noticed something odd - I can get full antialiasing up to 16x using up to Snowblind, but can't get AA on the original clients and RCs (after 1.20). 1.22 introduces some features I'd like to use so I tried updating but to no avail. Cool viewer doesn't work either.

Just wondering how AA works on your viewers when it doesn't seem to with others. Any information or help would be appreciated (I'm using the 178.24 Nvidia drivers).

Boy Lane said...

@Caliah

I'm not making a Cool Viewer for the RC in the moment. It is too buggy and too time consuming.

Please don't try to mix versions, it will not work.

Linda Brynner said...

Hi Nicholaz,

I am about to change to your viewer as SL drives me mad.
In 1.20 and 1.21 my experience is that the memory leak is less as i can stay online now for many hours without problems.

However 1.21 is severly slower on rendering. SL has recently upgraded graphics quality without given that choice to users. It's like they have implemented an automatic kind of anti-aliasing.
In 1.22 RC rendering is even dramatically worse.

Will try your viewer :)

Nicholaz "The Mad Patcher" Beresford said...

So far I could not make it leak to any gross extend (I'm not counting minor growth because that could even come from memory bubbles like the one about keyframemotion).

I'll try with their stock viewer first. Maybe they are using different libraries ... it wouldn't be the first time that a leak comes through use of a 3rd party library (unfortunately the collected a nice mix of libs which mix static and dynamic runtime environment). I'll also play with display settings.

Nicholaz "The Mad Patcher" Beresford said...

Linda,

trying my viewers or Henry/Boy's should really be worth trying.

Good luck ..


Markus

Caliah Lyon said...
This post has been removed by the author.
Caliah Lyon said...

@Boy I just meant that I was using Cool's latest release, not that there was a 1.22 or that I was mixing versions? Nothing appears to be working for me when it comes to AA but 1.20 or older at the moment, possibly because of what Linda mentioned. I suppose I will have to upgrade my card, but until then I'm stuck with Snowblind.

Boy Lane said...

@Caliah

I've made a test version of the 1.22.3 CV, please read the comments on my blog (not linked in the main posting). There's also a newer version of the 1.21. Both have some reported sound issues. I don't have much time this week to look into it, but you could give it a try. For the driver, the last properly working one is 175.19.

Garn said...

memory leaks? http://jira.secondlife.com/browse/VWR-11193 just happened to see the post and thought id toss it out incase some1 wanted to look into it lol

jeanRicard Broek said...

Hope to see you again soon Nicho.
Many things are now happening since you left Hippo & SL.