UPDATED (2x): OpenSauce and Halo CE Crashing *PLEASE TEST FOR FEEDBACK*

Doesn't solve anything for me.

And I finally remembered the term I was looking for: Memory leaks. After I installed OS, Halo has been getting LOTS of memory leaks, which persist AFTER I close Halo. I have to go end each individual leak manually. It's a pain in the ass.

This only happens on my desktop. On my laptop, it runs fine.

Quote:

---

Originally Posted by English Mobster

Doesn't solve anything for me.

And I finally remembered the term I was looking for: Memory leaks. After I installed OS, Halo has been getting LOTS of memory leaks, which persist AFTER I close Halo. I have to go end each individual leak manually. It's a pain in the ass.

This only happens on my desktop. On my laptop, it runs fine.

---

I didnt notice any memory leaks and I've spent hours opening and closing Halo last night working on something in OS.

I'm STILL getting memory leaks. I've now uninstalled and reinstalled three times, and it's still an issue. =/

There's probably something actually wrong with your computer or current operating environment.

I'm willing to bet that you have either outdated drivers for something or an app which is interfering with the memory of DirectX and Halo.


The only problem I experience with my computer is that sometimes Halo just doesn't exit (or always crashes on exit). But that's just Halo without any additions to it (other than maybe another d3d9 for Triplehead). I wonder if it has something to do with Windows Vista x64.

Quote:

---

Originally Posted by jcap

There's probably something actually wrong with your computer or current operating environment.

I'm willing to bet that you have either outdated drivers for something or an app which si interfering with the memory of DirectX and Halo.

The only problem I experience with my computer is that sometimes Halo just doesn't exit (or always crashes on exit). But that's just Halo without any additions to it (other than maybe another d3d9 for Triplehead).

---

But this only started happening after the installation of OS.

I'll still run a check to make sure I have all the current drivers, just in case.

If the memory leaks still happen even when OS is NOT loaded, then its not OS...

In the beginning there nothing, then there was an exception

and I was not pleased, I rested on all 7 days.

Then i deleted init.txt and I was happy.

Windows 7 64-bit

Code:

---

------------------
System Information
------------------
Time of this report: 7/8/2009, 23:02:08
      Machine name: mmmBop
  Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7137) (7137.winmain.090521-1745)
          Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK Computer Inc.       
      System Model: G50VT             
              BIOS: Default System BIOS
          Processor: Intel(R) Core(TM)2 Duo CPU    P8400  @ 2.26GHz (2 CPUs), ~2.3GHz
            Memory: 4096MB RAM
Available OS Memory: 4096MB RAM
          Page File: 2495MB used, 13891MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
  User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7137.0000 64bit Unicode

---

Code:

---

------------------
System Information
------------------
Time of this report: 7/12/2009, 15:17:47
      Machine name: RED-SEVEN
  Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7100) (7100.winmain_win7rc.090421-1700)
          Language: English (Regional Setting: English)
System Manufacturer: VIAP4X
      System Model: AWRDACPI
              BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: n/a
            Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
          Page File: 2016MB used, 2078MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
  User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7100.0000 32bit Unicode

---

Functions Properly
No exceptions, no errors. Gravity was modified with OpenSauce.

Halo CE does not completely close.
Forced to End Process after quitting Halo CE.

Quote:

---

Originally Posted by Truth Unknown

Halo CE does not completely close.
Forced to End Process after quitting Halo CE.

---

T'was my problem. Memory leaks. Now I know I'm not the only one who's getting those.
It IS an issue with OS, not the computer. No cure for it nor my missing chat woes as of yet.

I did some research, and I found one other person who was using a program VERY similar to OS for PC, who had encountered the same problem.

Unfortunately, he fixed it by getting a new video card/reformatting.
All my efforts to reinstall DirectX have failed. Every time, DirectX gives me a message saying that there is a newer or equivalent copy of DirectX installed. While that IS true, there is an equivalent copy installed, it's one which possibly has some broken files. DirectX eradicator thinks I'm running Vista when I'm really running XP with some modifications made to some system files (Something called Vistamizer), so I can't uninstall DirectX.

I think I've found what the hell I did to cause it, as well.
I was one of the first to jump onto the OS thread with this computer, before people explained I needed to put the d3d9.dll into my CE folder. Well, actually, I did put it into my CE folder, but the init.txt caused it to exception. But I didn't know that was what caused it, so I moved the d3d9 into my system32 folder, backing up the original and replacing it.
Now, Windows isn't letting me overwrite it with the backup, even though it was totally fine with me fucking it up in the first place. So I need to be able to delete that d3d9, overriding Windows' "protection" of the DirectX files, so I could reinstall the backup.

It's not OS, I think. It seems to be the issue with any d3d9.dll. Before I used OS, I used Software TripleHead, and I had the problem a lot. Now, I don't have the problem where it will remain in memory anymore, but I don't remember exactly when they stopped, if it happened immediately after I stopped using the dll.

I have been using the OS dlls since then, though all modified versions, and I'm not having any problems with it.