61 réponses à ce sujet

[Spaceweed10]

OverdoseBR wrote...

Still no memory leak fix. Hope they get around to doing that soon.

What memory leak?

Edit:

I've just checked my performance meter, and it seems the game isn't leaking memory, but using a lot.  I have 4Gb, and 62% of it is being used and it hasn't budged in 6hrs.

I have a Core2, 2.66 CPU and that is at 100%, and my GPU is a 260GTX.  I am running the game at max settings and so far it is running very smoothly.

The memory isn't 'leaking', so don't throw hearsay around.  The game is system hungry as indicated by the specs issued.  Take this into account when adjusting your settings for gameplay. 

Modifié par Spaceweed10, 06 novembre 2009 - 07:22 .

[Syrellaris]

OverdoseBR wrote...

Still no memory leak fix. Hope they get around to doing that soon.

That is because, it does not exist.

[tashtego9]

Is the patch listed on this site for digital versions (ie Direct2Drive) as well as boxed?

[sticks435]

Syrellaris wrote...

OverdoseBR wrote...

Still no memory leak fix. Hope they get around to doing that soon.

That is because, it does not exist.

Yea, I'm in agreement here. Anyone with this so called memory leak needs to check thier specs. I have 4GB of ram, and never have a problem. I even alt tabbed out after 8 hours of playing, and was only half used.

[r0gue9]

Windows7 64-bit

4 GB RAM



No "memory leak" issues at all. Played multiple sessions, 4-6 hours at a time. Even alt-tabbed out multiple times. No problems of any kind. No crashes, no extra long load times. Just smooth sailing.



The only problem I've had is that there's not enough hours in the day for me to play! WTB 30 hour days PLZ K THX!!

[Monthigos]

I'm not aware of any memory leak issues but my game does occasionally freeze up. I've got in the habit of frequently quick saving. Its not really an issue - usually when it crashes its time for me to take a break anyway.

[katt2001]

win 7 64bit here

8GB ram

quad core AMD



game runs smoothly for hours on end.



when i tab'd out the other night i saw the game using a touch over 2GB ram and 3 of my 4 cores.



it does love the resources.

[dawhip]

If there is no "leak" can someone please explain how to fix something? I'm running this on a dual core, 4GB, Vista x64 with a 9700M GT 512MB Video Card. The game runs perfectly on full specs for about 10 minutes then the stuttering starts. I have to shut the game down and start it back up for it to work. What could be causing this? I've turned all the settings off from v-sync to disabling sound effects to "low" settings but nothing is working.



My drivers are all up to date too...



Any help would be great!

[DrowNoble]

Seems to be a memory leak here too. The longer I play the lower the framerate gets and the longer the load times are. This is something that should of been caught in the QA part of development.



I can play Mass Effect on max settings with no issues, yet can't go more than 20-30 mins on DA before everything nearly stops working.

[Kolgorf]

For those that ran the patch and the launcher doesn't do anything and get a "side byside config" error running daorigins.exe you need the newest MS Visual c++ update:



http://www.microsoft...&displaylang=en



Download and install the "vcredist_x86.exe" file (this fixed it for me).



BTW: I did not discover this.

[Sprod Rossington]

Yay, it works again. Thank you.

[TheShady]

I wouldn't talk of memory leak but of simple bad memory management.

After about an hour of playing, the loading times get longer and everything generally lags a little.

Having 4GB of RAM here too.



The problem just seems to be that the RAM never is properly emptied, unnecessary data just sitting in the memory, cranking up load times. Also, try travelling to each place. Go from Orzammar to the Brecilian Forest, then visit a few places in Denerim and then go through Redcliffe town into the castle. Then try travelling back to Denerim. There's a severe increase of loading times as all those places, all the different data (textures, etc.) seems to just stay in the memory and isn't properly cleared.





Whatever it is, call it memory leak or anything else, the program grows slower the longer it runs while it should run at the same speed all the way through if properly programmed.