Virtual Memory, Hopper and your device

re: Virtual Memory, Hopper and your device

Varun W — Mon, 11 Aug 2008 14:54:09 GMT

Hi,

Should Hopper be run on apps with a GUI? When I run hopper on my device I get access violations with devhealth.exe which is getting launched by hopper. This app does not have a GUI so I was curious if Hopper can be run on apps with GUI only.

- Varun

re: Virtual Memory, Hopper and your device

Mark23 — Fri, 16 May 2008 03:11:36 GMT

You really know what you are talking about and can explain things really well.

re: Virtual Memory, Hopper and your device

haibo — Thu, 10 Apr 2008 13:23:07 GMT

There did have some problem ,when use the MemoRx.exe to check VM when use WMPLAYER.EXE in WM6.0.There will always show "#".But the VM is fine when you use devhealth.exe to check the device.

MemoRx incorrectly displaying VM overlap in WM6.1

HoppeRx - the cure for your ailing device — Fri, 11 Jan 2008 03:08:55 GMT

Many OEM’s have already noticed that Memory Doctor doesn’t correctly represent VM overlap in pre-release

re: Virtual Memory, Hopper and your device

Miller Fu — Fri, 09 Nov 2007 02:20:26 GMT

Hello Shende

I encountered a problem. I hope you can help explain. Thanks in advacne. According to memorx.exe debug message, the windows media player always is overflow when it plays a local file. But the device runs properly. No abnormal things happen. Is this a potential problem? Or it is a bug of Memorx.exe.

re: Virtual Memory, Hopper and your device

luckytigerwood — Wed, 04 Jul 2007 06:15:39 GMT

Hi shende:

Could you please help me to know, how to use powertoy - nkDebugx?

It just a DLL, and i can't find help document to use it ,thanks!

re: Virtual Memory, Hopper and your device

Jim Row — Mon, 25 Jun 2007 18:36:04 GMT

We been writing our own version of Memorx and the results we receive being quite close to MemoRX findings are not the same on several processess.

I am sure there are several others in the mobile development community who are doing the same and have the same question as I do...

Could you provide more details on how the "highest address" of allocated VM is computed for each process?

Heap Walking provides quite a bit of details but my upper memory address on several processes does not match with what Memorx reports. It would suggest an error in our computations, but where?

Kind regards,

JTR

re: Virtual Memory, Hopper and your device

Jason — Wed, 13 Jun 2007 03:42:25 GMT

Can you post the source or have MIPS/X86 build? thanks in advance

re: Virtual Memory, Hopper and your device

Ian — Thu, 08 Feb 2007 08:52:25 GMT

Is Dll low address fixed? or variant?

re: Virtual Memory, Hopper and your device

Jim Row — Tue, 19 Dec 2006 19:42:55 GMT

Is MemoRx source available (possibly as Open Source) to allow for customization and further enhancements ?

Thanks!

JimR