View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000763 | FSSCP | DirectX | public | 2006-01-31 03:45 | 2006-05-08 04:14 |
| Reporter | mehere101 | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0000763: Memory Leaks During Normal Gameplay using D3D | ||||
| Description | FSO invariably leaks memory, causing framerate drops. This is NOT a graphics issue, because the frame rate does stabalize at 120fps-75fps between leaks then the game stutters, then it's OK, then it stutters... | ||||
| Additional Information | Windows XP, 1gb ram, 120gb hard drive, 3ghz Pentium 4 Hyper threading, ATI Radeon 9600 with Catalyst 5.3 | ||||
| Tags | No tags attached. | ||||
|
2006-01-31 03:45
|
|
|
|
Not sure what version of FS2_Open you are using, but try something newer. Also use OGL instead of D3D as D3D has known memory leaks. Edit: Also, are you using the MediaVPs? They use a good chunk of memory and you may just be running low rather than it actually being a big memory leak. edited on: 01-30-06 23:07 |
|
|
I'm using the P4 specific version, 3.6.7. edit: I ran the debug version (hence fs.log), it repeatedly told me that a vec3d was null I might add that my computer can handle even the most recent games and that it is NOT my computer having troubles with graphics. edited on: 01-31-06 22:30 |
|
|
Have you tried using OGL yet? Also, try using one of the newer CVS builds. |
|
|
I switched to OGL and it works fine. Still, I'm Using ATI, and ATI has a bad reputation with OGL drivers |
|
|
Yeah but there isn't much to do about that. The D3D code has numerous bugs as well as the memory leaks and may be totally dropped soon. OGL is really the only choice if you want this fixed, that is, unless you are a coder will fix the D3D problems yourself. I'll leave this bug open for a couple of more days in case someone wants to take a look at the D3D issues but after that this will just have to be considered non-fixable for D3D. |
|
|
3.6.7 isn't very stable anyway. I think some of those crashing problems have been fixed in later versions and aren't present in the old 9/17 version either as far as I know. |
|
|
Guess no one cares to fix D3D so this sucker is getting... Closered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-01-31 03:45 | mehere101 | New Issue | |
| 2006-01-31 03:45 | mehere101 | File Added: fs.log | |
| 2006-01-31 04:06 | taylor | Note Added: 0004578 | |
| 2006-01-31 04:07 | taylor | Note Edited: 0004578 | |
| 2006-01-31 04:08 | mehere101 | Note Added: 0004579 | |
| 2006-02-01 03:30 | mehere101 | Note Edited: 0004579 | |
| 2006-02-20 23:53 | taylor | Note Added: 0004855 | |
| 2006-02-21 02:28 | mehere101 | Note Added: 0004860 | |
| 2006-02-21 03:28 | taylor | Note Added: 0004863 | |
| 2006-02-21 03:29 | taylor | Severity | crash => major |
| 2006-02-21 03:29 | taylor | Status | new => acknowledged |
| 2006-02-21 03:29 | taylor | Category | graphics => DirectX |
| 2006-02-21 03:29 | taylor | Summary | Memory Leaks During Normal Gameplay => Memory Leaks During Normal Gameplay using D3D |
| 2006-02-21 03:54 | CP5670 | Note Added: 0004866 | |
| 2006-05-08 04:14 | taylor | Status | acknowledged => closed |
| 2006-05-08 04:14 | taylor | Note Added: 0005481 |
