Steamlimiter crashes steam

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Launch steam
2.Activate 'steam limiter'
3.

What is the expected output? What do you see instead?

When I launch steam limiter before or after launching steam, steam crashes.

What version of the product are you using? On what operating system?

Steam Limiter 0.7.0.3 on Windows XP.

Please provide any additional information below.

Original issue reported on code.google.com by fallout_...@hotmail.com on 4 Dec 2013 at 11:01

[GoogleCodeExporter]

Edit: It only happens when I select 'Filter Content Servers' on steam limiter.

Original comment by fallout_...@hotmail.com on 4 Dec 2013 at 11:03

[GoogleCodeExporter]

OK, I just checked and steam-limiter is still running 100% fine for me here on 
Windows XP (both before and after the latest Steam client update), so we have a 
bit of a mystery. Ideally if I could make it happen here it'd be easy to fix, 
but it's working fine for me so we need to go looking for clues as to why.

Fortunately, Steam itself has an error capture facility, and in the Steam 
install folder there should be a directory called "dumps", inside which it will 
store a capture of part of the Steam process as it was at the time it actually 
crashed - these files are normally uploaded to Valve for detailed analysis, but 
for me I should be able to load it into Visual Studio and see how far it got 
into my stuff.

Having a file or files in that directory isn't evidence of a problem by itself, 
as Steam tends to store these not just on real crashes, but for all kinds of 
internal diagnostics that aren't problems. In your case though, if Steam is 
actually failing due to steam-limiter then there should be a file with a .DMP 
extension being created when you run through the steps which reproduce the 
failure.

If so, then it would be helpful if I could inspect that file; these files are 
automatically uploaded to Valve, so by design they don't aim to capture any 
private information, but if you're curious as to what they contain the gory 
details are all here - 
http://infopurge.tumblr.com/post/10445418822/the-format-of-a-minidump-mdmp-file

It's hard to know what it might be able to tell me - often these dump files 
aren't very useful because they happen after the fact, often long after the 
point at which things start to go off the rails - but it's at least a starting 
point and every so often you get lucky and they point right at the cause, and 
if nothing else it's a place to start.

If you zip up the most recent .DMP file and either attach it here (or e-mail it 
to me if you're more comfortable doing that), I can take a look and see whether 
it gives me any hints as to the root cause of why things are failing on your 
system.

Original comment by nigel.bree@gmail.com on 5 Dec 2013 at 3:37

• Added labels: OpSys-Windows, Usability

[GoogleCodeExporter]

Issue 29 has been merged into this issue.

Original comment by nigel.bree@gmail.com on 5 Dec 2013 at 3:38

[GoogleCodeExporter]

I've confirmed as an interaction between steam-limiter and an optional 
component of ZoneAlarm in 2003 and 2004 versions, IMSecure. This component of 
ZoneAlarm was withdrawn from the market and pulled out of the product in 2005 
so this shouldn't have affected many people - people with newer verions of 
ZoneAlarm from 2005 on won't have this component.

The root cause is a small bug in steam-limiter interacting with a small bug in 
IMSecure, so I've checked in a likely fix for my end of the problem which 
should resolve this. A test version 0.7.0.4 has been built and is available in 
the test build folder, 
https://skydrive.live.com/redir?resid=5A7B4FB9B40CCAFD%21126 for confirming the 
resolution.

Original comment by nigel.bree@gmail.com on 9 Dec 2013 at 2:52

• Changed state: Fixed