Memory Leak?
#226
Posté 06 janvier 2010 - 05:11
#227
Posté 06 janvier 2010 - 06:00
My system:
(Copy-Pasted from Dragon Age configuration tool)
OS: Microsoft Windows 7 Professional
CPU: Intel® Core i5 CPU 750 @ 2.67GHz
Physical Memory : 3,99 GB (2 sticks of 2 GB ram each)
VRAM: 1,00 GB
GPU: ATI Radeon HD 5700
I'm gonna try that "use one core only" solution and see if it works. I'll try to remember to report my findings! I'll be using the CPU labeled "0" (mine are labeled 0-3).
#228
Posté 06 janvier 2010 - 06:28
StreetBushido wrote...
So, after 2 months from the OP this issue still hasn't been fixed? I thought it was something to do with my computer when I noticed that the load times got increasingly longer the longer i played. It is a bit of a "relief" that it's an issue with the game.
My system:
(Copy-Pasted from Dragon Age configuration tool)
OS: Microsoft Windows 7 Professional
CPU: Intel® Core i5 CPU 750 @ 2.67GHz
Physical Memory : 3,99 GB (2 sticks of 2 GB ram each)
VRAM: 1,00 GB
GPU: ATI Radeon HD 5700
I'm gonna try that "use one core only" solution and see if it works. I'll try to remember to report my findings! I'll be using the CPU labeled "0" (mine are labeled 0-3).
What driver are you running? I noticed with the included driver with my 5770 that the game had serious loading issues, but when i cleared it out and went to the 9.11 driver everything was fixed.
#229
Posté 06 janvier 2010 - 06:34
StreetBushido wrote...
So, after 2 months from the OP this issue still hasn't been fixed? I thought it was something to do with my computer when I noticed that the load times got increasingly longer the longer i played. It is a bit of a "relief" that it's an issue with the game.
My system:
(Copy-Pasted from Dragon Age configuration tool)
OS: Microsoft Windows 7 Professional
CPU: Intel® Core i5 CPU 750 @ 2.67GHz
Physical Memory : 3,99 GB (2 sticks of 2 GB ram each)
VRAM: 1,00 GB
GPU: ATI Radeon HD 5700
I'm gonna try that "use one core only" solution and see if it works. I'll try to remember to report my findings! I'll be using the CPU labeled "0" (mine are labeled 0-3).
You don't want to use 0. That's the system core and I heard some people had some bad crashes when using just 0.
Modifié par FFMagee, 06 janvier 2010 - 06:34 .
#230
Posté 06 janvier 2010 - 09:04
FFMagee wrote...
You don't want to use 0. That's the system core and I heard some people had some bad crashes when using just 0.
Thanks for the heads up! I'll go with 1 and try now. I got caught up in some Left 4 Dead 2 and haven't had time to experiment
#231
Posté 06 janvier 2010 - 09:33
... There's no such thing as a "system core." Sure, you might be referring to the BSP, but that can be any core, and once the APIC has been switched to symmetric I/O mode the BSP becomes just another core/processor unless the operating system chooses to treat it differently, which Windows doesn't. Some drivers may want to run exclusively on core 0(Or 1, or 2, or 3... etc etc), but that doesn't make that core a "system core."FFMagee wrote...
StreetBushido wrote...
So, after 2 months from the OP this issue still hasn't been fixed? I thought it was something to do with my computer when I noticed that the load times got increasingly longer the longer i played. It is a bit of a "relief" that it's an issue with the game.
My system:
(Copy-Pasted from Dragon Age configuration tool)
OS: Microsoft Windows 7 Professional
CPU: Intel® Core i5 CPU 750 @ 2.67GHz
Physical Memory : 3,99 GB (2 sticks of 2 GB ram each)
VRAM: 1,00 GB
GPU: ATI Radeon HD 5700
I'm gonna try that "use one core only" solution and see if it works. I'll try to remember to report my findings! I'll be using the CPU labeled "0" (mine are labeled 0-3).
You don't want to use 0. That's the system core and I heard some people had some bad crashes when using just 0.
The more you know...
Modifié par Arpl, 06 janvier 2010 - 09:33 .
#232
Posté 06 janvier 2010 - 10:28
Since this problem takes a while to manifest I wonder if it's not related to the loading times that grow longer.
#233
Posté 07 janvier 2010 - 01:05
Arpl wrote...
... There's no such thing as a "system core." Sure, you might be referring to the BSP, but that can be any core, and once the APIC has been switched to symmetric I/O mode the BSP becomes just another core/processor unless the operating system chooses to treat it differently, which Windows doesn't. Some drivers may want to run exclusively on core 0(Or 1, or 2, or 3... etc etc), but that doesn't make that core a "system core."FFMagee wrote...
StreetBushido wrote...
So, after 2 months from the OP this issue still hasn't been fixed? I thought it was something to do with my computer when I noticed that the load times got increasingly longer the longer i played. It is a bit of a "relief" that it's an issue with the game.
My system:
(Copy-Pasted from Dragon Age configuration tool)
OS: Microsoft Windows 7 Professional
CPU: Intel® Core i5 CPU 750 @ 2.67GHz
Physical Memory : 3,99 GB (2 sticks of 2 GB ram each)
VRAM: 1,00 GB
GPU: ATI Radeon HD 5700
I'm gonna try that "use one core only" solution and see if it works. I'll try to remember to report my findings! I'll be using the CPU labeled "0" (mine are labeled 0-3).
You don't want to use 0. That's the system core and I heard some people had some bad crashes when using just 0.
The more you know...
Well, then I guess I'm just talking crazy talk. I could've sworn I saw other people warn against that.
#234
Posté 07 janvier 2010 - 05:54
By around 2 hours and 20 minutes of gametime (just my play session, not the character), I noticed the performance of the game starting to hit the wall. By about 2 hours and 45 minutes into playtime, transition from dialog back to being able to play took about 11 seconds. At 3 hours 45 minutes in, it took 114 seconds to go from the Apprentices' Quarters to the 2nd Floor of the Tower of Magi.
My PC:
Windows 7 Ultimate 64-Bit
6 GB DDR3 1333 MHz RAM
nVidia 280 GTX
Intel Core i7 920 (2.6 Ghz) - I had all cores running
Actual combat is fine, and once I'm in dialog, I have no issues. However, it's the transitioning that gets worse and worse as my session continues.
#235
Posté 07 janvier 2010 - 12:27
Hopefully we'll get a fix!
Windows Vista 64bit
Intel Quad Q9550
Nvidia Geforce 285 GTX
6 Gig Ram
#236
Posté 07 janvier 2010 - 03:54
i just found out that i have 4GB of save files. no slowdown though
#237
Posté 07 janvier 2010 - 04:04
#238
Posté 07 janvier 2010 - 09:23
#239
Posté 07 janvier 2010 - 09:41
end3ffect wrote...
I pre-ordered the game because I was so excited about it. I got the game, loaded it up and from the beginning was in love...until the slowdowns. I refuse to play this game until it is fixed. I would expect Bioware- one of the leading game companies in the world would have caught such a major flaw in their game. If this doesn't get fixed, the game won't be played and I will withdrawl my pre-order of Mass Effect 2 for fear of memory leaks. Thanks Bioware... You have made part of the gaming community less trustworthy of you in a world that relies on trust.
I find your idea of cancelling ME 2 idiotic as the UE 3.5 engine used in ME 2 doesn't have memory leaks what so ever. I am ashamed of you fearing an Epic Games Game Engine over a problem with BIOWARE's own internal GAME ENGINE. UE 3 does have a problem with texture filtering and poor PC code optimization though, but BioWare got that all down already with ME 2 and UE 3.5. So don't go boycotting other games over a problem that doesn't relate the the other game's engine. This memory leak is solely the problem of DA: O's engine which is INDEPENDENT of ME 2's engine.
Also a lucky soul out there might have taken your Collector's Edition Pre-Order now. Heh.
#240
Posté 07 janvier 2010 - 10:14
After having run DA on a single core I noticed the following:
-On a single core the game ran somewhat more unevenly and special effects took their toll on the framerate.
-Load times still crawled upwards over time.
EDIT: Almost forgot
-The transition from conversation to game became longer as well as the regular loading times.
I then restarted the game and ran on all four cores, and for a while the load times were instantaneous but it didn't take long (less than 30 minutes) before the loading times had elongated, but at least not alot. They had gone from imperceptible to up towards 10 seconds or more. This may have had to do with me travelling to larger, more populated areas of the game, I don't know.
Anyway, those are my results. Sadly I'm afraid they don't add much to the total equation.
Modifié par StreetBushido, 07 janvier 2010 - 10:16 .
#241
Posté 07 janvier 2010 - 11:01
#242
Posté 07 janvier 2010 - 11:25
It seems the most critical fix in this update was Firefox running out of memory when the user has had a web site open for two hours or more that contains "active content" such as Facebook, online board gaming sites like scrabble...etc.
bugzilla.mozilla.org/show_bug.cgi
I wonder...how many of us that have experienced the slowdown after several hours of DA:O also had Firefox running in the background? It's been a week or two since I've played, but I generally have firefox open as long as the computer is on. So it's a fair bet it was always running when the game was running.
#243
Posté 07 janvier 2010 - 11:37
#244
Posté 07 janvier 2010 - 11:45
whtnyte-raernst wrote...
I just had an interesting read following the recent Firefox update.
It seems the most critical fix in this update was Firefox running out of memory when the user has had a web site open for two hours or more that contains "active content" such as Facebook, online board gaming sites like scrabble...etc.
bugzilla.mozilla.org/show_bug.cgi
I wonder...how many of us that have experienced the slowdown after several hours of DA:O also had Firefox running in the background? It's been a week or two since I've played, but I generally have firefox open as long as the computer is on. So it's a fair bet it was always running when the game was running.
I don't have Firefox.
#245
Posté 08 janvier 2010 - 12:14
Memory leaks do not exhibit themselves in that manner, they generally don't affect performance until you completely run out of memory, in which case you crash or start swapping tons of pages to disk (Edit: or initiate a GC cycle or the likes, but DAO does not use a GC as far as I can see). Since you have 6GB RAM and DAO can't use more than 2GB, it's extremely unlikely that it's the latter case, and since it doesn't crash outright it cannot be the former.FFMagee wrote...
Well, I have found some more evidence that would point towards a memory leak. I was tracking info for my computer in the process of failing to prove that DA:O was overheating my computer. I was using a stopwatch to track when what I assumed was my processor fan would kick into overdrive. It never happened, but I got some other information that's fairly interesting.
By around 2 hours and 20 minutes of gametime (just my play session, not the character), I noticed the performance of the game starting to hit the wall. By about 2 hours and 45 minutes into playtime, transition from dialog back to being able to play took about 11 seconds. At 3 hours 45 minutes in, it took 114 seconds to go from the Apprentices' Quarters to the 2nd Floor of the Tower of Magi.
My PC:
Windows 7 Ultimate 64-Bit
6 GB DDR3 1333 MHz RAM
nVidia 280 GTX
Intel Core i7 920 (2.6 Ghz) - I had all cores running
Actual combat is fine, and once I'm in dialog, I have no issues. However, it's the transitioning that gets worse and worse as my session continues.
Please, for the love of $deity, stop talking about things you don't have any idea about, that goes for all of you; all you're doing is spread misinformation. A gradual slowdown does not equate to a memory leak.
Modifié par Arpl, 08 janvier 2010 - 12:15 .
#246
Posté 08 janvier 2010 - 12:33
Ease up there Arpl, even among those of us with computer science degrees there's been debate on what constitutes a "memory leak."Arpl wrote...
Please, for the love of $deity, stop talking about things you don't have any idea about, that goes for all of you; all you're doing is spread misinformation. A gradual slowdown does not equate to a memory leak.
It's just a generic term everyone has been using to refer to a symptom rather than a long explanation.
My definition of a memory leak may vary from your definition. It depends a lot on who your professors were in college.
#247
Posté 08 janvier 2010 - 01:02
#248
Posté 08 janvier 2010 - 01:04
Oerwinde wrote...
I don't know if its the memory leak but I encounter the 5 minute load times after playing for a half hour or so, plus slowdowns(Will run fine when the game first starts, but after a while suddenly becomes choppy). Also combat will lag. Game will be running fast, but combat will go through 5-6 attacks before the first one registers. I'll run around attacking grunts once, then focus on a boss and suddenly all those grunts I attacked once will start dying in the order I attacked them.
Windows XP Pro
Pentium D 3.2 GHz
3 GB RAM
Geforce 9800 GTX
Ya I got almost the same problem, but the combat lag is what really annoys me. Queuing up 5 attacks and waiting 20 seconds and then have them fire off at once, only to see the enemy dead as well as yourself...
Modifié par OfTheFaintSmile, 08 janvier 2010 - 01:06 .
#249
Posté 08 janvier 2010 - 01:13
Then I'd like to hear your definition of a memory leak...whtnyte-raernst wrote...
Ease up there Arpl, even among those of us with computer science degrees there's been debate on what constitutes a "memory leak."Arpl wrote...
Please, for the love of $deity, stop talking about things you don't have any idea about, that goes for all of you; all you're doing is spread misinformation. A gradual slowdown does not equate to a memory leak.
It's just a generic term everyone has been using to refer to a symptom rather than a long explanation.
My definition of a memory leak may vary from your definition. It depends a lot on who your professors were in college.
#250
Posté 08 janvier 2010 - 01:50





Retour en haut




