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.

kill what process? explorer?

SDB15 said:

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.

Click to expand...

And in addition to what sup3rsprt said, where and how are you observing the memory leak?

SDB15 said:

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.

Click to expand...

What's a "memory leak" ?

chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia

thefabe said:

chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia

Click to expand...

I thought they might have changed the definition of the word-pair.

...can only be diagnosed by a programmer with access to the program source code...

Click to expand...

chuckr said:

thefabe said:

chuckr your being sarcastic right? Memory leak - Wikipedia, the free encyclopedia

Click to expand...

I thought they might have changed the definition of the word-pair.

...can only be diagnosed by a programmer with access to the program source code...

Click to expand...

Click to expand...

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.

H2SO4 said:

I think we're going to have fun here

Click to expand...

Me too...

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.

Click to expand...

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.

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.

Click to expand...

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.

chuckr said:

guess that depends on what you mean by 'diagnose'.
In the OP, it seems to mean 'observe' the memory leak.

Click to expand...

Agreed. They're using "diagnose" as in "diagnosis: there's a memory leak".

chuckr said:

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.

Click to expand...

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

chuckr said:

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.

Click to expand...

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".)

chuckr said:

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.

Click to expand...

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

H2SO4 said:

We should probably take it up elsewhere though, to give the OP their thread back

Click to expand...

I agree....

H2SO4 said:

We should probably take it up elsewhere though, to give the OP their thread back

Click to expand...

Something just struck me, at the barbie:

Congratulations on your new 'Guru' badge !!!

You certainly are most deserving of it...
unlike many others here
umoh

Chuck

sup3rsprt said:

kill what process? explorer?

Click to expand...

I think an answer to this would be a great place to start with. I also didn't expect such a response to just posting what wikipidia stated. I should be more careful in the future i recon. fabe

thefabe said:

sup3rsprt said:

kill what process? explorer?

Click to expand...

I think an answer to this would be a great place to start with.
I also didn't expect such a response to just posting what wikipidia stated.
I should be more careful in the future i reckon. fabe

Click to expand...

Au contraire !

Post away - that's what we're here for.

Wikipedia is not 100% accurate all the time, so we can discuss here what might
possibly be 'errors' in the "documentation".

If I'm not mistaken, anybody can edit anything on that site.

Sorry its taken me so long to reply. I am using multimeter gadget to monitor my memory use. I am dual booting windows vista and 7 using C as my vista drive and X as my windows 7 drive when I select multiple word files in C drive (across the partition) from windows 7, the memory leaks until it has no more space. If I'm quick I can usually get a command line up and get task manager running before it locks up. Then I kill windows explorer process and type explorer.exe in the command line to reopen it.

SDB15 said:

Sorry its taken me so long to reply. I am using multimeter gadget to monitor my memory use. I am dual booting windows vista and 7 using C as my vista drive and X as my windows 7 drive when I select multiple word files in C drive (across the partition) from windows 7, the memory leaks until it has no more space. If I'm quick I can usually get a command line up and get task manager running before it locks up. Then I kill windows explorer process and type explorer.exe in the command line to reopen it.

Click to expand...

Does the same symptom occur if you boot into safe mode and try copying the files in the same way?

Chances are it's going to be something like the anti-virus filter driver.

H2SO4 said:

chuckr said:

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...

Click to expand...

... 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".)

Click to expand...

Not to let this "fall through the cracks", as regards "object files" produced by an "assembler":

See this link: MASM32

( Slightly modified: )
Why Write Assembler
The simple answer is because you can. While there are very good compilers that in many instances produce good quality code when run with the right options, you are usually stuck with doing things their way where with an assembler as powerful as MASM you have a high degree of architectural freedom which you manipulate to your design advantage to produce high precision high performance code without compromise to language format or compiler designer preference.

MASM's flexibility allows the skilled programmer to target areas as diverse as dynamic link libraries for 'various programs', object modules that are linked directly into 'various programs' and of course complete executable files for task critical applications. MASM when mastered correctly put power and performance into the hands of programmers that few have ever seen and contrary to popular opinion, a modern assembler like MASM, used in conjunction with both macros and libraries, can be coded at about the same speed and reliability as 'other' code.

Click to expand...

An even more important point here, is that with a really good disassembler,
the output mnemonics can be used as "source-code" input to an assembler,
to yield a dll or an object file.

chuckr said:

H2SO4 said:

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

Click to expand...

Not to let this "fall through the cracks", as regards "object files" produced by an "assembler":

Click to expand...

I stand corrected. It is indeed possible for an assembler to produce a binary which technically qualifies as an "object file", but I'd argue that the overwhelming percentage of object files are compiled, not assembled.

chuckr said:

An even more important point here, is that with a really good disassembler,

the output mnemonics can be used as "source-code" input to an assembler,
to yield a dll or an object file.

Click to expand...

That still doesn't make the disassembled mnemonics the "source code" for the original executable, just as using a really good DAT recorder to grab Beethoven's 9th Symphony off the radio doesn't mean I now have access to his sheet music

H2SO4 said:

using a really good DAT recorder to grab Beethoven's 9th Symphony off the radio doesn't mean I now have access to his sheet music

Click to expand...

I'd transcribe it for ya arranged for guitar, heh. One of my favorite pieces of all time!

H2SO4 said:

That still doesn't make the disassembled mnemonics the "source code" for the original executable, just as using a really good DAT recorder to grab Beethoven's 9th Symphony off the radio doesn't mean I now have access to his sheet music

Click to expand...

Indeed it does, IFF the resultant binaries are identical, byte-for-byte...
(If they're not, then you'd have to tweak the mnemonics to 'fit' the original .exe binary.)

I can't believe that you, of all people, would record the Choral "off the radio"...

However, if you had a really, really, excellent "Demusiker",
and your A/D converters were of excellent quality, one would never know:



I hope it was Toscanini's version...

Tochter aus Elysium,Freude, schöner Götterfunken

Click to expand...

Perhaps Rachmaninoff's 2nd Piano Concerto could be an early test-trial of the "Demusiker"
since it's more familiar to many people, and a little less complicated...

i have the same problem

SDB15, I have the same problem, when i select any word files on explorer the memory consumption goes up 100% and freeze up the machine. This problem only happens with word files (Microsoft word 2007).... Do you solve the problem????.

OS . Win 7