Hammer bug?

[Limpet]

If you open a map then bring up the properties dialog, close the map and then try and close the dialog does hammer crash and then say that some memory cant be read for you?
Does for me, I think I understand why, but just wondering if this has been addressed before.

 

[asdjkgeidg]

NO! something valve made has bugs? HAHAHHA
try it on another system. if it does the samething then it is a bug. if it doesn't. then update your GPU drivers/motherboard. bla bla bla

 

[Limpet]

heh
Well I would but I dont have another system

 

[RoyalEF]

Memory can't be read is usually a message caused by antivirus products. If your program and AV aren't gtting along this would be common.

However, the Halflife game is the first program that I see generate this error often. Maybe this is a XP SP2 artifact that anytime a memory does a GPF, we now get memory can't be read instead. Each time HL crashed with this is was because I map I compiled exceeeded the engine and ... sadly instead of drawing less or drawing slower, HL crashes instead. :flame:

 

[Limpet]

I have no antivirus programs running, and this is no big deal just wondering if other poeple have noticed it too. All I have to do is close out the properties dialog before I close hammer or the dialog.