Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Scuddie on July 25, 2004, 03:13:57 am

Title: What could be a BIG problem!
Post by: Scuddie on July 25, 2004, 03:13:57 am
OK, this whole memory leak thing is really starting to scare me.  

Here's the deal.  This afternoon, I decided to finish up the main FS2 campaign.  I started the game with -timerbar enabled, just to see how demanding it was on my system.  Most of the time it was 2 red bars, with the occasional 10.  I got to the last level, and I was fighting off some bombers, and one caught me by surprise and got the better of me.  I was tired of playing, so I just decided to hit shift+esc to quickly end it, but instead, the whole screen went black, except there were red lines all the way down the screen.  I waited for 5 minutes.  I could hear events happening in the background.  I hit my hotkey to start winamp to play whatever was loaded at the time, and It was responding.  However, I still only saw a red and black striped screen, with the FS2 cursor dead center.  Since I couldnt see what was going on, I couldnt do a restart, so I just hit the reset button.

Well, here I am, 5 hours later, astonished at how WMCoolmon can make a total of 9 replies in about 5 minutes, and then suddenly, something WAY out of the ordinary happens.  My entire screen fills up with random graphical artifacts.  About a split second later, it shows up as an understandable image.  Every second line of pixels was red.  There were recognisable elements, such as the HUD showing between the lines.  They were all in really weird places.  I also saw a large chunk of recognisable debris, namely the collossus being destroyed (the game hung for about 10 seconds when that happened).  I also saw what looked like to be a few explosion sprites in random areas, clipping with other elements.

So, in closing, I'd like to know WTF just happened!  In my 10 years of computer expertise, I have NEVER seen anything like this, and I would expect it even less coming from a luke-warm boot.  Is it possible that the memory leaking protected memory, as in resident even during a soft reset?  I'd really like to know what's going on.
Title: What could be a BIG problem!
Post by: WMCoolmon on July 25, 2004, 03:22:36 am
Are you saying that this happened outside of Freespace 2? :wtf:

Sounds like somehow, the contents of the video card's memory were written to the screen...maybe some stuff was saved in the virtual memory pagefile and an errant call loaded and displayed it again?
Title: What could be a BIG problem!
Post by: Kazan on July 25, 2004, 04:05:49 am
sounds like a textbook example of a  VRAM paging error
Title: What could be a BIG problem!
Post by: kasperl on July 25, 2004, 09:04:38 am
That would be fun to replicate......

Any chance on this leading us to the memory leak?
Title: What could be a BIG problem!
Post by: Kazan on July 25, 2004, 11:29:25 am
the probablility of that is between 0 and 0
Title: What could be a BIG problem!
Post by: jdjtcagle on July 25, 2004, 11:35:53 am
Really I'm taking new pics and can't get past "ONE" mission :(

It's starts out really good, but then taht leak hits and all hell breaks loose on Fs_Open
Title: What could be a BIG problem!
Post by: Scuddie on July 25, 2004, 09:27:39 pm
OK, this is really irritating me.  So far, since yesterday, I have gotten a total of three "VRAM paging errors", all from missions resembling the ones played in D3D.  One was what looked to be a collage of items, another was a set of 32x32 (guestimation) tiles, but it was all from one mission (I could tell because it was a subspace mission).  The last one I got was what looked like a direct screen capture.  The same screen I saw as FS2 crashed and caused a reboot.  All of these, as I have said before, were taken from D3D instances of FS2.  I tried replicating the problem with OpenGL, and to no avail.  Is this something that would merrit a mantis entry, or does it sound like my video card is dying...  But only from D3D??  I have updated my drivers after the second instance, and that obviously didnt help.