|In dynamic memory allocation, after the program terminates and one forgets to deallocate the memory, will that memory stay allocated?|
| by Allan in Programming Languages|
Been reading C++ books but I can't seem to find the answer. All I know
is dynamic memory allocation such as when I make a function:
int * ptr = new int;
It allocates a memory and returns that memory to the
pointer, however, since the pointer is a local variable, after the
memoryleak(), the pointer which contains the reference
|How to get memory bandwidth from memory clock/memory speed|
| by Will in Web Design|
FYI, Here are the specs I got from Nvidia
Note that the memory speed/memory clock are the same thing on their
website and are both measured in Gbps.
|PDFLibNet.dll: Attempted to read or write protected memory. This is often an indication that other memory is corrupt|
| by Douglas Stockwell in Web Design|
I'v got a wierd problem in visual studio 2005,
I'm worrking with
ASP.Net v2 and I'm using the PDFLibNet.dll to convert a specific page into
image with the folowing code:
PDFLibNet.PDFWrapper doc = null;
string nomcomplet =
publication.PublicationFilesPath + "V" +
publication.VersionUsed.ToString().PadLeft(6, '0') + "" + fichier;
= new PDFLibNe
|CUDA: are access times for texture memory similar to coalesced global memory?|
| by Wonderbread in Databases|
My kernel threads access a linear character array in a coalesced
fashion. If I map
the array to texture I don't see any speedup. The
running times are
almost the same. I'm working on a Tesla C2050 with
compute capability 2.0 and read
somewhere that global accesses are
cached. Is that true? Perhaps that is why I
am not seeing a difference
in the running time.
|ASP.NET / IIS6: Attempted to read or write protected memory. This is often an indication that other memory is corrupt|
| by slpnshot in Programming Languages|
I'm getting the following error on my production servers:
Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.
happen all the time, but seems to happen most frequently during times of
The error is occurring in a custom
The stack trace
|cocoa 64bit binaries leak memory? (releasing NSData does not free memory)|
| by Luxembourg in Programming Languages|
i've been playing some time with different builds of my application and
there seem strange things to happen:
my app has a 5mb idle
footprint. when uploading a file memory in size of the file is reserved.
after the upload the reserved memory should be freed. now there are
differences in the builds (gc = garbage collector):
no-GC: all memory is freed instantly.
|Error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt|
| by kpkp in Programming Languages|
I have both VS 2005 and 2008 installed on my machine. 2005 is fine. For
2008, literally any asp.net project I try to create gets this eror. I try
stepping into the code, and the error occurs apparently before anything
that I can trap is loaded. There is no information written to the event
I have tried this with a "Hello World" webpage with
nothing else going on. Seems uniq
|Error: Attempted to read or write protected memory this is often an indication that other memory is corrupt|
| by Enar in Programming Languages|
I am getting the error stating in title in the following program.
am trying to impersonate the user.
Here my code base.
|Memory problem in Winforms application - Memory increases on each search and bind activity|
| by André Rocheleau in Programming Languages|
I have memory problem in my application. Each time I fetch data from db
and assign it to Grid, memory increases and sometimes when extensive
searches are made the memory reaches to 1 G.B.
There can be
other memory handling issues but to test that searching and binding data
repeatedly consumes good amount of memory I have created a new winforms
application and drop a button and a gri
|Real memory utilization Vrs “Live” Memory in XCODE tools|
| by JustinDSN in Programming Languages|
Our application uses the GPUImage Framework to process images. We're
utilizing just about every filter and blend mode within the framework.
We're allocating and releasing memory as we should. But, in spite of the
fact that our "Live" memory stays at about 2.5MB sometimes spiking to 10MB
but dropping back to 2.5MB, the app, will without a doubt, crash after
saving about 13 images out that use ov