AppDefend and Physical Memory Access...

When appdefend asks for memory access from a specific program, everything freezes or slows down for a bit then allows you to press allow or block. Is that nromal? For instance, Ewido.

dja2k

 

Hi Dja2k,

I don't think its normal for your system to slow down for no reason. However if you install software like Ewido (you will have to ask the authors themselves what it does) there is a chance that it can use CPU time and appear to slow down your system, simply by doing what it is designed to do.

The physical memory access alert from AppDefend however, is no different to any other alert and there is no reason why that in particular should slow down your system.

 

When that alrert comes up it DOES slow down the system dramatically on ALL my PC's. Always has. AppDefend is PREVENTING this access until you allow it. If the program needs to access memory and you dont let it, common sense says there will be some negative effect, Agreed? All my games do this as well.

No offense man but come on.......dont send this guy on some wild goose chase looking for solutions when it is OBVIOUS APpDefend and the prevention of access to physical memory is the problem...maybe by design but it is a probelm nevertheless.

 

Hi Kegel,

It is impossible for AppDefend to cause the slowdown, because it suspends the operation in a NON cpu wasting way. As such the only waste cpu cycles must be coming from elsewhere.

Just because AppDefend makes the system exhibit a symptom doesn't mean the problem wasn't there to begin with.

 

It wasnt there to begin with and goes away when the program is disabled. PG displays the same behaviour. Trust me on this one man...its the app. Mostg Games will absolutely crash if you dont allow physical memory access BEFORE you launch the game as once you lauch it is usually too late....the mouse freezes or moves at like a pixel a minute....sometimes the game outright crashes. I dont use AD any longer because of this and have limited myself to RegDefend only. Its too cumbersome to have to add everything manually. I end up having to have almost every app I use in the exceptions list (lots of .net apps)...seems kind of counter productive.

 

Hi Kegel,

Your problem and the original posters problems are two different things. DirectX or OpenGL applications seem to require physical memory access to work correctly, as you pointed out. And they don't seem to handle being blocked from doing so in a fashion which you would consider elegant. I have been looking into this for a future build to help games work better with AppDefend.

AppDefend is an advanced utility which ALTERS the way the system works, as such some applications which are hard-coded to work a certain way may not appreciate it being changed. It is up to me as the developer to work around these situations.

The original posters question was relating to slowdown in regards to a physical memory alert. I was just pointing out how it couldn't be AppDefend. If you want to start a new thread about physical memory access and directx/opengl applications then please feel free to do so.

 

Sorry Jason, but it is AppDefend! Check out my other thread... https://www.wilderssecurity.com/showthread.php?t=104673&highlight=dja2k And actually no it is not just ewido. Winamp, WMP, Media Player Classic, Limewire, and some websites that use java routine like chat rooms do it too. They all cause the same thing, slowdown until you allow access to physical memory. Now the point is Process Guard used to do that too, not so much of a slowdown like AppDefend, but DiamondCS never found an explaination for it, so I thought maybe I was dealing with a new deck of cards with AppDefend.

dja2k

 

Hi Dja2k,

I know it seems like AppDefend, but it is just a symptom which AD happens to show you. There is better handling of physical memory for such applications in the next build.

 

Thanks Jason, that is all I needed to hear....

dja2k

 

I've received many alerts for programs trying to access Physical Memory. Without exception, each time the alert appeared, the system was almost 100% frozen. Even moving the mouse cursor is near impossible--each time, I have to guess where the cursor needs to go, because it doesn't move in real time, it freezes and them jumps suddenly after several seconds of a near-total system freeze.

This has happened to me with all sorts of applications, including Media Player Classic, BurnInTest Pro, Everest, the application I use to join video files, Firefox (yes, Firefox!), RivaTuner, Google Earth, javaw.exe (for Azureus), rundll32.exe, Virtual PC, and many more. I don't think that these are all OpenGL/DirectX-related applications.

 

Try this Jason

If you can go through the speed tests here http://www.dslreports.com/stest without problems I will be surprised. I was getting the above described symptoms every time if IE was not set to "allow" for physical memory access prior to launching the test.

 

Thats the same thing I would do

dja2k

 

It IS ApDefend that casuses this. End of question.

PG does the same thing.

 

To all those who are having this problem. Can you please explain to me what exactly it is you are doing? I haven't experienced any of the symptoms you guys are talking about.

As a matter of fact, everything here is running very smoothly on my Windows XP Pro machine.

nameless1, you say it happens to you with firefox. I am using firefox right now with no problem. AD doesn't even mention anything about firefox wanting physical memory access.

dja2k, you say it happens while using Winamp, Windows Media Player, Media Player Classic, and Limewire. Well, I am using all four of them with not a single problem.

Strange...

 

here's what i think

First java is really strange, it need memory access and if that java file actually is an applet opened by the browser, the one who need memory access became the browser.

SO my guess 1 is java.
That cover ie / firefox memory acess ( and limewire )

My guess two is some king of codec
Winamp, Windows Media Player, Media Player Classic

are file that are use to encode or decode audio and video
maybee they need special memory acess.

 

If i am rigth about codec then i should see that some file does crash appdefend and other dont.

The kind of file that use mostly harmless codec would be uncompressed wav file. You can file alot of those in your C:\WINDOWS\Media folder

The worst kind of codec is mp3 protected by drm... especially when they bundle a rootkit

but my guess is that this happened when you tryed to see a video.
Gspot is a really powerfull tool to indetify the codec used by an avi file
http://www.headbands.com/gspot/

 

I use PG (ver. 3200) and Appdefend (ver 1.110) side by side and I, like suave, have no problems. Everything runs really smooth. But it is a well known fact that there is no program that is compatible with every computer configuration on earth. Some are bound to have problems, maybe you guys belongs to them?
Thats why "try before you buy" is such a great concept

 

Once physical memory is allowed, there are no problems here either.

Just a logical question: IF a program needs to access physical memory to run properly, and IF a program blocks that access initially, is it logical to assume that there would be some kind of negative effect on that program? ....at least until you AALLOW the access? Im not saying ApDefend doesnt work as once you tweak it, it is pretty much there and you can forget about it. BUT...we are pointing this out so that POSSIBLY there can be a workaround for programs that need this access.

forget it.

 

As Jason has noted above, AppDefend will suspend the process until you respond to its prompt so the program itself should not cause any problems. However there may be other processes linked to that program (mouse driver DLLs, other security software, etc) and it may be these that are causing the problems, especially if they are waiting on that program to complete an action (e.g. antivirus software trying to gain access to a resource held by that program in order to scan it).

I encountered absolutely no issues with PG and its Physical Memory control but did have system lockups with System Safety Monitor when it tried to prompt for programs attempting such access. Ultimately, how these features work will depend on your system configuration and software setup so if you are encountering problems and want to try to find a solution, try removing or disabling other software to see if you can identify the conflict.

 

Instead of paying attention to smug "Haha, nanapoopoo, I have no problems, try before you buy " answers, and random guesses, I'll wait for Jason to give more insight.

 

Please refrain yourself from infantilising those who are trying to relp you.

I hardly see what jason can give more on that topic
Your application request for physical memory, the request is hold in a non cpu wating way until you accept it. ( this is what appdefend do)

As paranoid2k clearly explained this particular thread does not freeze cpu.
However, linked thread can be the problem and there is definitively some devlopment that can be done to minimise those situation.

In any cases just turn off that particular feature and wait until next beta

From Jason:

The other way to *debug* your problem is to identify what exactly conflict with appdefend in a more precise way. This will help both yourself and Jason to solve teh confict. And unfortunately this is pretty much trial and error, and this is where "random guess", as you call them, comme handy.

 

Well put f3x.

My comment was not meant to be bad in any way. I just thought that when I have particular problems, I do appriciate comments from people who do not have the same problem with whaeverprogram. Then I know that it is not the whateverprogram that is the problem.
I can then start looking at my setup trying to find what in my configuration it is that causes this particular problem since no one else or very few has the same problem.

Maybe I could have refrained myself from praising the shareware concept tho. point taken.

 

Sorry, I took the comment as nose-thumbing, and every time I re-read it, I see the same thing. I apologize for being mistaken.

But it doesn't always work that way. The fact that not everyone has this problem with AD does not mean that it isn't AD at fault, or at least partially at fault. It only means that there is probably some compatibility issue.

In any case, here is some of the other software I run, in case anyone else who purchased AppDefend impetuously sees a commonality:

WinXP
AnyDVD
NOD32
CommView
SpeedFan
Nero 6
RivaTuner
TrueCrypt
VMware Workstation
Virtual PC 2004

 

hi nameless1
i've been reporting *random* freezin for alot of reason ( not necerserly phisical memory ) Since then i did some cleaning, one of the thing i have removed is anyDVD, please give it a try. In my case my sistem is now stable.

I do not know if any of the two use a kernel driver,
CommView
SpeedFan

If they do, try disabling them temporaly

Have a nice holliday
hope this help

 

My system runs very well in all cases except during physical memory alerts from AD.

They each use two kernel drivers! (For CommView, they are cv2k1 and ts_lb, and for SpeedFan, they are giveio and speedfan--though I have giveio disabled.)

If I get ambitious enough, I will go on a disable/test rampage.