Command and Conquer: Renegade Official Forums: Mod Forum » Memory leak in Visual C++ 2005 (non-SP1) standard library

Home » Renegade Discussions » Mod Forum » Memory leak in Visual C++ 2005 (non-SP1) standard library

Show: Today's Messages :: Polls :: Message Navigator

Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301803]

Sat, 08 December 2007 08:30

Yrr
Messages: 556
Registered: October 2006
Location: Germany

Karma: 0

Colonel

Hello together.

While looking for a strange memory leak on the Renegade Community Marathon server, I found a leak in the standard library of Visual C++ 2005 (more precise, in istream and ostream classes). The problem affects all modifications using STL istream and ostream classes (e.g. for file IO) such as SSGM for example.
When googling for the problem, I found out that the bug has been fixed with Service Pack 1 and suggest, that you upgrade if you not yet did so.

Information: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID= 98861

Download: http://www.microsoft.com/downloads/details.aspx?FamilyID=7b0b0339-613a-46e6-ab4d -080d4d4a8c4e&DisplayLang=en
(you need the file VS80sp1-KB926748-X86-INTL.exe, 43.5 MiB)

Greetings,
Yrr

Yrr.

Creator of...
Resurrection, a Command & Conquer: Renegade Modification
LevelRedit, a .mix to .lvl converter

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301805 is a reply to message #301803]

Sat, 08 December 2007 08:38

Sir Kane
Messages: 1701
Registered: March 2003
Location: Angerville

Karma: 0

General (1 Star)

istream, ostream, etc. suck anyways.

Proud N9500 and proud N6270 user. Creator of the IEE libraries (original bhs.dll) and the RB series software.

http://n00bstories.com/image.fetch.php?id=1189992501

http://www.n00bstories.com/image.fetch.php?id=1257492907

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301854 is a reply to message #301805]

Sat, 08 December 2007 13:04

Ethenal
Messages: 2532
Registered: January 2007
Location: US of A

Karma: 0

General (2 Stars)

Sir Kane wrote on Sat, 08 December 2007 09:38

istream, ostream, etc. suck anyways.

What do you use then?

-TLS-DJ-EYE-K wrote on Mon, 18 March 2013 07:29

Instead of showing us that u aren't more inteligent than a Toast, maybe you should start becomming good in renegade Thumbs Up

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301858 is a reply to message #301803]

Sat, 08 December 2007 13:33

Yrr
Messages: 556
Registered: October 2006
Location: Germany

Karma: 0

Colonel

I don't use the STL too and just wanted to inform those who do.

Yrr.

Creator of...
Resurrection, a Command & Conquer: Renegade Modification
LevelRedit, a .mix to .lvl converter

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301862 is a reply to message #301803]

Sat, 08 December 2007 13:52

jnz
Messages: 3396
Registered: July 2006
Location: 30th century

Karma: 0

General (3 Stars)

Quote:

What do you use then?

fstream

FILE *

string

char *
wchar_t *

cout
cin

printf
scanf

ostringstream

sprintf

istringstream

sscanf

I'm glad i got out of using them too.

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301866 is a reply to message #301862]

Sat, 08 December 2007 14:43

Sir Kane
Messages: 1701
Registered: March 2003
Location: Angerville

Karma: 0

General (1 Star)

RoShamBo wrote on Sat, 08 December 2007 14:52

fstream

FILE *

HANDLE

Proud N9500 and proud N6270 user. Creator of the IEE libraries (original bhs.dll) and the RB series software.

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301871 is a reply to message #301803]

Sat, 08 December 2007 14:57

jnz
Messages: 3396
Registered: July 2006
Location: 30th century

Karma: 0

General (3 Stars)

difference?

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301872 is a reply to message #301854]

Sat, 08 December 2007 14:57

cnc95fan
Messages: 1260
Registered: July 2007

Karma: 0

General (1 Star)

Ethenal wrote on Sat, 08 December 2007 14:04

Sir Kane wrote on Sat, 08 December 2007 09:38

istream, ostream, etc. suck anyways.

What do you use then?

Don't you mean "How do you use them?" Razz

Sorry, lol, I saw the oppertunity and I took it. Very Happy

Cabal8616 wrote on Sun, 27 April 2008 15:50

I say a personal fanning of the genitals would be awesome.

RA3 AUTOMATICLY SUCKS
www.battlefordune.co.uk

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301873 is a reply to message #301872]

Sat, 08 December 2007 15:00

Ethenal
Messages: 2532
Registered: January 2007
Location: US of A

Karma: 0

General (2 Stars)

cnc95fan wrote on Sat, 08 December 2007 15:57

Ethenal wrote on Sat, 08 December 2007 14:04

Sir Kane wrote on Sat, 08 December 2007 09:38

istream, ostream, etc. suck anyways.

What do you use then?

Don't you mean "How do you use them?" Razz

Sorry, lol, I saw the oppertunity and I took it. Very Happy

No I don't. I mean exactly what I said.

-TLS-DJ-EYE-K wrote on Mon, 18 March 2013 07:29

Instead of showing us that u aren't more inteligent than a Toast, maybe you should start becomming good in renegade Thumbs Up

Report message to a moderator

Re: Memory leak in Visual C++ 2005 (non-SP1) standard library [message #301886 is a reply to message #301871]

Sat, 08 December 2007 15:34

Sir Kane
Messages: 1701
Registered: March 2003
Location: Angerville

Karma: 0

General (1 Star)

Less bloated and faster.

Proud N9500 and proud N6270 user. Creator of the IEE libraries (original bhs.dll) and the RB series software.

Report message to a moderator

Previous Topic:	need help modding
Next Topic:	Server-Side Objects.ddb(.gm) restrictions

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri May 03 08:42:35 MST 2024

Total time taken to generate the page: 0.00731 seconds