How can I find more than one leak in the compile log?

obodobear

L4: Comfortable Member

• 

Mar 15, 2016

172

32

• Jan 26, 2017

• #1

Okay, so I do not know if this is possible to do, but if it is then it would help me out significantly. A map I have about finished still has multiple leaks in it that I am aware of, so I am just going around right now fixing them up. However the process has been really painstakingly slow, because I just have to compile the map over and over again fixing the one leak it tells me about. Is there any way I could find leaks quicker, or find more in the compile log? If so please let me know.

 

Vel0city

func_fish

aa

• 

Dec 6, 2014

1,947

1,589

• Jan 26, 2017

• #2

You can't, unfortunately. VBSP will stop once it finds a leak even if there are many leaks. You have to go at them one by one.

Why? Source, that's why.

 

• 
  1

obodobear

L4: Comfortable Member

• 

Mar 15, 2016

172

32

• Jan 26, 2017

• #3

Well... In that case it's going to be a long day.

 

Crowbar

Spiritual preprocessor

aa

• 

Dec 19, 2015

1,455

1,297

• Jan 26, 2017

• #4

Technically, there's not just one or many leaks. And no way to determine "how many", theoretically (that word is meant to mean, really no damn way. Not because of limits). It's just that the map has leaked, or not.

 

Crash

func_nerd

aa

• 
• 
• 
• 

Mar 1, 2010

3,319

5,500

• Jan 26, 2017

• #5

You can set it to a vbsp only compile, which is conveniently one of the fastest steps. You don't have to do vvis or vrad at all to find leaks.

 

• 
  1
• 
  2

Dr. Orange

aa

• 

May 25, 2015

390

307

• Jan 26, 2017

• #6

Even better, add -leaktest to the expert compile options and it will stop compiling once it's hit a leak.

 

• 
  3

Pocket

Half a Lambert is better than one.

aa

• 

Nov 14, 2009

4,696

2,580

• Jan 26, 2017

• #7

Eight years, and I'm just now learning that parameter exists. Is there any way to alter the default compile settings so that's always there?

 

Dr. Orange

aa

• 

May 25, 2015

390

307

• Jan 27, 2017

• #8

You have to add it to the expert compile options for VBSP (or if you have a batch file). However, from what I understand, it only runs just enough of VBSP to generate a leak from most sources, meaning a file created when using -leaktest probably isn't fully compiled. Therefore -leaktest should only be used when, well, testing for leaks.

 

Pocket

Half a Lambert is better than one.

aa

• 

Nov 14, 2009

4,696

2,580

• Jan 27, 2017

• #9

Well, obviously. It's more of a "not having to remember to do a VBSP-only compile every single time before a full one" thing. If the process visibly aborts in the first few seconds, I'm not gonna think I got a finished map out of it.