447 réponses à ce sujet

[Kelston]

I hate solutions that are "cripple your hardware" aka force your quad core to run on 1 core. ):

[Joel171]

Guy4142 wrote...

Nope, i've seen people with intels complain about the exact same issue. Might be Quad related?

Nope, I run on a dual core and have the same problems.

[Wirehead-1]

bump

i'm having this trouble as well. huge load times and poor play peformance. Seems to increase in time the longer I play.

Not running an AMD or a multi-core system.

Cheers

[JironGhrad]

Draetor wrote...

I'm pretty sure the game has some sort of memory leak. When I first launch the game, it uses about 50-55% of my 4GB RAM on Windows 7 64-bit. After a couple hours of playing, my RAM usage hovers 75-80%. So basically, instead of clearing from the memory, it only adds to it. Eventually, there would be an overload or extreme page file usage (causing long load times and slowness). People with huge amounts of RAM (4GB or better, 6GB) won't notice it as much because they have a lot of RAM to make up for the leak.

I've explained this issue in detail multiple times.  Certain processors (mostly AMD x2s and x4s, but also Intel Core 2 Quads and even some of the i7s) are having difficulty releasing threads as the processor switches the application from core to core. It switches the cores so it can load and unload at the same time which "should" (when the processor is following the directions correctly) actually speed things up greatly. Instead, the processor retains some of the allocated RAM in what is effectively a "ghost process": RAM that's not being used but is allocated anyway.  Setting Core affinity to 1 core (and 2 sometimes works for Quads) stops the game from passing the application around and eliminates the lost RAM.

There are people who complain or worry about using only 1 processor and taking a performance hit... BUT... the game and your OS will work around your core usage... so if CPU 1 is the set core and it's doing the game the OS will not assign anything else to it, so you effectively get the whole core as dedicated to the game.

Further, it should affect "everyone" equally if it were a leak, and while there are people with all OS's having problems it doesn't affect every user.

Modifié par JironGhrad, 15 novembre 2009 - 06:57 .

[JironGhrad]

Wirehead-1 wrote...

bump

i'm having this trouble as well. huge load times and poor play peformance. Seems to increase in time the longer I play.

Not running an AMD or a multi-core system.

Cheers

What are your system specs?

[Galaxyrise]

JironGhrad: None of that work is done by the CPU, it's done by the operating system. If there is a leak, it is very unlikely to be in Windows, but either a driver (unlikely) or the game itself.



Limiting an application to just one CPU can change the way that application runs, masking bugs that only happen when two parts of the program run simultaneously. With the game only allowed to use one core, those two parts of the program will likely run one after the other instead.

[Ardikus]

I remember seeing a semi-fix on the main daforums bioware forums for AMD processors, but sadly those forums were taken down. Does anyone have a link to this semi-fix that a mod posted in that thread?

[JironGhrad]

Ardikus wrote...

I remember seeing a semi-fix on the main daforums bioware forums for AMD processors, but sadly those forums were taken down. Does anyone have a link to this semi-fix that a mod posted in that thread?

That fix is located in the Troubleshooting FAQ sticky up top.

Galaxyrise wrote...

JironGhrad: None of that work is done by the CPU, it's done by the operating system. If there is a leak, it is very unlikely to be in Windows, but either a driver (unlikely) or the game itself.

Limiting an application to just one CPU can change the way that application runs, masking bugs that only happen when two parts of the program run simultaneously. With the game only allowed to use one core, those two parts of the program will likely run one after the other instead.

The problem with your statement (and if you had read any of my posts about what constitutes an actually memory leak you'd know) is that it doesn't affect all multi-core users and it doesn't affect all processors of the same model even (because there are different versions of the same model). If it were a true memory leak (and not something with the processor) then it would affect everyone equally.

[D_Thoran]

The game runs perfectly, with no problems, all settings on high. The only thing I am experiencing is longer and longer load times as the game goes on, and my cpu usage meters stay pegged at 100%.



I am amd dual core 2.4ghtz, 4 gig ram, nvidia 9 series 1 gig card.



no way the cpu's should be pegged like that. Bioware needs to address this asap, as it can be causing damage to people's systems to run this game.

[Galaxyrise]

" If it were a true memory leak (and not something with the processor) then it would affect everyone equally." That is simply not true. You can certainly have a memory leak that only occurs under certain timing conditions, or only in certain configurations.



I never even claimed it was a memory leak. For me, I edited the PEH to enable LargeAddressAware and the problems went away (memory use stops growing), suggesting that the game uses more than 2G of virtual address space in certain configurations but may not leak at all.

[madatea]

extreme loading sequences after about 60 minutes of playing. after restart it's smooth again.

Using amd x2 5600, 3gig ram, xp sp3.

[DJPhased]

I can confirm the same symtoms as well, the RAM gradually gets eaten, and my CPU goes through the roof.

[Khpuffy]

I get this. Sometimes it's after 1 hour, sometimes after 4. Worst part is I'm running a Pentium 4.

[stubbieAussie]

If this is of any help.

I get no memory leak according to my Logitech G15 RAM monitor (stays at 48%) as well as no slowdown after 5 hours of game play.

specs:

Intel Core2 Duo CPU E8500 @ 3.16GHz

ATI Radeon HD 4870 512meg using Catalyst 8.12 drivers (old but good)

4gig RAM

windoze XP SP2

Sound Blaster X-Fi Xtreme Audio

[KCFender]

I would strongly suggest AGAINST people running the game on one core as a fix. Not only am I highly doubtful that it really fixes anything for most PCs, but this game is having a problem with over-taxing the CPU. Why put all that heat, and wear-and-tear on one CPU? Just doesn't seem healthy to me.

[webejames]

ive been running the game for quite sometime now there are some issue to be fixed but remember is brand new . i am running an i7 2.96 quad core with 9 gigs of ddr3 ram on a rampage 2 gene board with a nivida gtx 260 with windows 7 64 . ive seen stuff like this the ram page file is huge if you dont have at least 4 gigs its gonna slow you down some . this game was ment for high end computers . with windows 7 you can use dx11. subfiles which compress the page files down alot ,heck i barely hit 30% cpu useage at any given time and page files barely hit 2gigs . couple of things that might help lag turn the graphics down to half so your page files arent so big remember your online as well. That could casue some problems if you have a few computers running at the sametime .

[vancheat]

i am having the same problem, but the drop in fps happens much quicker. within about 10 minutes of the game running smoothly (30+ fps), my fps drops below 5. tried all graphical settings, same results.



running 2.2 duo

4 gb ram

geforce 9700 gt 512 mb



any suggestions?

[Jaconium]

JironGhrad wrote...

Draetor wrote...

I'm pretty sure the game has some sort of memory leak. When I first launch the game, it uses about 50-55% of my 4GB RAM on Windows 7 64-bit. After a couple hours of playing, my RAM usage hovers 75-80%. So basically, instead of clearing from the memory, it only adds to it. Eventually, there would be an overload or extreme page file usage (causing long load times and slowness). People with huge amounts of RAM (4GB or better, 6GB) won't notice it as much because they have a lot of RAM to make up for the leak.

I've explained this issue in detail multiple times.  Certain processors (mostly AMD x2s and x4s, but also Intel Core 2 Quads and even some of the i7s) are having difficulty releasing threads as the processor switches the application from core to core. It switches the cores so it can load and unload at the same time which "should" (when the processor is following the directions correctly) actually speed things up greatly. Instead, the processor retains some of the allocated RAM in what is effectively a "ghost process": RAM that's not being used but is allocated anyway.  Setting Core affinity to 1 core (and 2 sometimes works for Quads) stops the game from passing the application around and eliminates the lost RAM.

There are people who complain or worry about using only 1 processor and taking a performance hit... BUT... the game and your OS will work around your core usage... so if CPU 1 is the set core and it's doing the game the OS will not assign anything else to it, so you effectively get the whole core as dedicated to the game.

Further, it should affect "everyone" equally if it were a leak, and while there are people with all OS's having problems it doesn't affect every user.

Have anyone tried reducing to 1 core and found out that this works?

[larstat]

I ran 2 days in a row for 6 hours each straight and never once did I slow down on a i7 processor.

[Naturalus]

Could somebody clarify if this is memory address problem witch means that 32bit systems run out of memory addresses and hang up becouse of it? Some other games that use a lot of memory addresses have suffered from same issue like Empire Total War.

If only 32bit Vista and XP users suffers from this then it is memory address problem and kind of operating system problem but it also partly Bioware problem too becouse they didnt tell that game require 64bit operating system or it run out of memory addresses.

Modifié par Naturalus, 20 novembre 2009 - 02:18 .

[PedrodeMexico]

There is clearly some sort of resource leak... and I'm 99% sure that the leak was not there in 1.0.... I did not have the "longer and longer load times" issue in 1.0 but it's there in 1.01



Clearly the devs need to address this... particularly because I believe it was introduced in 1.01

[TehLost_Hope]

Nope, happens to me and I'm still running 1.0.

[jercrow]

I am also still playing an unpatched version and experience increased load times over time as well as near 100% CPU everytime I check. Adjusting core affinity made no difference on my load times, but I did see some lag in large battles that has never been an issue when playing on both cores. It also dropped my CPU usage to near 50% at all times, which, if I understand correctly, is really saying that the single core is running as at 100%.



While affinity adjustment may work for some, it is clearly not a "fix," just a stopgap measure to treat the symptoms.



Windows XP 32bit (2002) SP3

AMD Athlon x2 4600 @ 2.41 GhZ

2G RAM

NVIDIA GeForce 8600 GTS

[Black--Hand]

Naturalus wrote...

Could somebody clarify if this is memory address problem witch means that 32bit systems run out of memory addresses and hang up becouse of it? Some other games that use a lot of memory addresses have suffered from same issue like Empire Total War.

If only 32bit Vista and XP users suffers from this then it is memory address problem and kind of operating system problem but it also partly Bioware problem too becouse they didnt tell that game require 64bit operating system or it run out of memory addresses.

Its not a memory address issue. I've tried on Windows 7 64 with 6 GB RAM and enabled large address awareness on the dragon age exe to no avail. After a somewhat random amount of time (sometimes 30 mins, sometimes 4 hours), the load times start increasing drastically.