Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Memory Leak when Copying/Selecting Word files

25 Sep 2009   #1

Windows 7 Pro
 
 
Memory Leak when Copying/Selecting Word files

I wondered if anyone has had similar problems or knew of a fix. Every time I select a word file on my c drive (which is the partition that holds my old vista files) the memory leaks and my machine freezes up until I can kill the process.

My System SpecsSystem Spec
.

25 Sep 2009   #2

XP, Seven, 2008R2
 
 

kill what process? explorer?
My System SpecsSystem Spec
25 Sep 2009   #3

Win7x64
 
 

Quote   Quote: Originally Posted by SDB15 View Post
I wondered if anyone has had similar problems or knew of a fix. Every time I select a word file on my c drive (which is the partition that holds my old vista files) the memory leaks and my machine freezes up until I can kill the process.
And in addition to what sup3rsprt said, where and how are you observing the memory leak?
My System SpecsSystem Spec
.


25 Sep 2009   #4

XP_Pro, W7_7201, W7RC.vhd, SciLinux5.3, Fedora12, Fedora9_2x, OpenSolaris_09-06
 
 

Quote   Quote: Originally Posted by SDB15 View Post
I wondered if anyone has had similar problems or knew of a fix. Every time I select a word file on my c drive (which is the partition that holds my old vista files) the memory leaks and my machine freezes up until I can kill the process.
What's a "memory leak" ?
My System SpecsSystem Spec
25 Sep 2009   #5

Windows 7 ultimate 64 bit / XP Home sp3
 
 

chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia
My System SpecsSystem Spec
27 Sep 2009   #6

XP_Pro, W7_7201, W7RC.vhd, SciLinux5.3, Fedora12, Fedora9_2x, OpenSolaris_09-06
 
 

Quote   Quote: Originally Posted by thefabe View Post
chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia
I thought they might have changed the definition of the word-pair.

Quote:
...can only be diagnosed by a programmer with access to the program source code...
My System SpecsSystem Spec
27 Sep 2009   #7

Win7x64
 
 

Quote   Quote: Originally Posted by chuckr View Post
Quote   Quote: Originally Posted by thefabe View Post
chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia
I thought they might have changed the definition of the word-pair.

Quote:
...can only be diagnosed by a programmer with access to the program source code...
I think we're going to have fun here

The Wikipedia entry is a bit ambiguous (while accusing others of n00bery). It is entirely possible to diagnose a memory leak without access to app source or any type of code-level analysis. A process whose commit charge keeps on increasing in the absence of commensurate workload increases, to the point where it either runs into it's maximum size limit or artificially prevents itself from doing so, is absolutely leaking.

What they presumably mean is that one cannot fix the leak without source code, which is also technically incorrect. For example, perhaps the thing was written in assembly and there is no higher-level source to speak of.
My System SpecsSystem Spec
27 Sep 2009   #8

XP_Pro, W7_7201, W7RC.vhd, SciLinux5.3, Fedora12, Fedora9_2x, OpenSolaris_09-06
 
 

Quote   Quote: Originally Posted by H2SO4 View Post
I think we're going to have fun here
Me too...

Quote:
The Wikipedia entry is a bit ambiguous (while accusing others of n00bery). It is entirely possible to diagnose a memory leak without access to app source or any type of code-level analysis. A process whose commit charge keeps on increasing in the absence of commensurate workload increases, to the point where it either runs into it's maximum size limit or artificially prevents itself from doing so, is absolutely leaking.
I guess that depends on what you mean by 'diagnose'.
In the OP, it seems to mean 'observe' the memory leak.

The word-pair used to mean c-programmers requesting free memory blocks for their code, then never releasing said memory back to the 'free-pool' in the OS.
The Memory Manager would then have those blocks marked as 'in use', when in fact they were not. But still being consumed.
That was considered 'memory-leak', along with other factors.
Eventually, the sum of these 'in-use' marked blocks, though not in use, would consume, etc.

Quote:
What they presumably mean is that one cannot fix the leak without source code, which is also technically incorrect. For example, perhaps the thing was written in assembly and there is no higher-level source to speak of.
Here, 'diagnose' would mean "repair".
I agree with "cannot fix the leak without source code", and I believe it is technically correct:
An 'assembler' requires source code (mnemonics) as input, to generate the computer's binary op-codes, etc. as an object file for linkage, etc. to generate the .exe executable...

You're not confusing 'assembly' with 'machine code', are you?

"Higher level" source is not required -- Assembly, of itself, is source code.

Viz:
This was for radar antenna 'Ellipticity Measurement' analysis on an MPS-36 radar at the Kwajalein Missile Range.
(See there, they changed the 'terminology' again...)
Ronald Reagan Ballistic Missile Defense Test Site - Wikipedia, the free encyclopedia
Had to find 'half-power' points at all quadrants, as well as determine the 'Full-power' point.

The code was called from a 100 pps 'Interrupt handler', which also gathered Elevation, Range, time-code, and other stuff.

This was my first run-in with Microsoft, regarding errors in their documentation:
The ordering and quantity of parameters on the stack.
I had determined the necessary corrections required for their documentation and received their 'prima donna' attitude.
It was also the last.


Attached Files
File Type: txt GETAZ_ASM.txt (1.8 KB, 30 views)
My System SpecsSystem Spec
27 Sep 2009   #9

Win7x64
 
 

Quote   Quote: Originally Posted by chuckr View Post
guess that depends on what you mean by 'diagnose'.
In the OP, it seems to mean 'observe' the memory leak.
Agreed. They're using "diagnose" as in "diagnosis: there's a memory leak".

Quote   Quote: Originally Posted by chuckr View Post
The word-pair used to mean c-programmers requesting free memory blocks for their code, then never releasing said memory back to the 'free-pool' in the OS.
Yes. For what it's worth, I wasn't disagreeing with anything you said in your previous posts. My issue was with Wikipedia's wording

Quote   Quote: Originally Posted by chuckr View Post
I agree with "cannot fix the leak without source code", and I believe it is technically correct:
An 'assembler' requires source code (mnemonics) as input, to generate the computer's binary op-codes, etc. as an object file for linkage, etc. to generate the .exe executable...

You're not confusing 'assembly' with 'machine code', are you?

"Higher level" source is not required -- Assembly, of itself, is source code.
Assembly is only the "source" if the executable was written in assembly. Otherwise, if the app was written in C, then the "source" files will be text representing C code. Ditto C++, C#, Java...

Once we agree on those semantics, I think we'll both be on the same page regarding the feasability of rectifying memory leaks through analysis of the disassembled mnemonics - with no access to the original source code.

(As a minor off-topic point, "object files" are produced by a compiler, not by an "assembler".)

Quote   Quote: Originally Posted by chuckr View Post
This was my first run-in with Microsoft, regarding errors in their documentation:
The ordering and quantity of parameters on the stack.
I had determined the necessary corrections required for their documentation and received their 'prima donna' attitude.
It was also the last.
A calling convention mismatch of some sort? I'd be interested to hear about your respective positions on the mechanics of that issue. We should probably take it up elsewhere though, to give the OP their thread back
My System SpecsSystem Spec
27 Sep 2009   #10

XP_Pro, W7_7201, W7RC.vhd, SciLinux5.3, Fedora12, Fedora9_2x, OpenSolaris_09-06
 
 

Quote   Quote: Originally Posted by H2SO4 View Post
We should probably take it up elsewhere though, to give the OP their thread back
I agree....
My System SpecsSystem Spec
Reply

 Memory Leak when Copying/Selecting Word files




Thread Tools



Similar help and support threads for2: Memory Leak when Copying/Selecting Word files
Thread Forum
chkdsk high memory usage / memory leak Performance & Maintenance
General Win7 memory leak and Unknown memory usage? Performance & Maintenance
Troubleshooting Excessive Memory Use (Memory Leak?) after playing vid. Performance & Maintenance
Memory consumption when copying files / installing Performance & Maintenance
Copying large files consumes too much memory General Discussion
Copying files to USB flash memory freezes win7 Hardware & Devices
More word on the 7100 RC Leak News

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:07 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33