In order to facilitate your predecessors, I would have to make a long story short

I wrote a small program in VB debugging when only around 100 k memory footprint

But more than 2000 after generated EXE running memory footprint, is this why??

How to solve this problem, thank you guys!

CodePudding user response:

If you exit code USES is the End of the program, may be you this kind of situation, although the End is also on behalf of the End of the program, but will not be released from memory resources..

If you program exit code with Unload Me, on the other hand, Unload the Me is the program exits and release resources from the memory..

In addition to check:
Finally close the window to open file also closed??

CodePudding user response:

2 m memory, random loading pictures, documents such as it is easy to reach 2 m, if have frequent use of memory and timely release (as if also has a timely release or use), the memory will be rising...

CodePudding user response:

"Little" to what extent?
2000 k is only 2 m, this should be including the VMM,
Basically is a normal phenomenon,
Run in the IDE, similar to "take care" in VB6,
Is interpretive mode, the memory footprint certainly isn't counted in the VMM,
As long as you are in the process of running,
The memory footprint is not "increasing",
Are expanding (already data memory except)
Basically can think a problem,

CodePudding user response:

I was looking for a finished product before writing program

When debugging is probably around 2000 k

But when generated exe memory reached 6000 ~ 8000 amazing occupancy rate

Why debugging with generated exe gap so big

CodePudding user response:

Its memory occupancy rate has been rising, stewards computer memory test can rise from 45% to 70%

Can you tell me where the problem is, why has been rising,

I use the variable is an array, also wrote to release part of the control with and control group

But don't understand why such a big gap,

CodePudding user response:

Memory is most probably in the task manager is around 8000 k

Software takes up more memory than this program also has, but obviously after open software

Memory, system operation is slow, it is what reason,

CodePudding user response:

refer to 6th floor yunsnow response:

task manager is present in most probably around 8000 k

Software takes up more memory than this program also has, but obviously after open software

Memory, system operation is slow, it is what reason,

Might be caused code logic problem, apply for inner and failed to release,
Even in the frequent application & amp; Release, under normal circumstances is also has a certain growth, growth had stalled,

CodePudding user response:

If memory has always been on the rise, there is a memory leak,
May
A) no release call external resources,
B) VB object when the circular reference does not automatically release (see the VB help circular reference index)
Detailed reference "senior Visual Basic programming (Advanced Visual Basic)" circular reference chapter 6

CodePudding user response:

refer to the eighth floor Tiger_Zhao response:

if memory has always been on the rise, is a memory leak,
May
A) no release call external resources,
B) VB object when the circular reference does not automatically release (see the VB help circular reference index)
A detailed reference "senior Visual Basic programming (Advanced Visual Basic)" circular reference chapter 6

Download learning!

CodePudding user response:

Some memory has not been released (such as: no form without unload, the Timer is running, etc.),
If you want to know the specific reason, it is better to put the program on the Internet, to find the reason,

CodePudding user response:

refer to the eighth floor Tiger_Zhao response:

if memory has always been on the rise, is a memory leak,
May
A) no release call external resources,
B) VB object when the circular reference does not automatically release (see the VB help circular reference index)
A detailed reference "senior Visual Basic programming (Advanced Visual Basic)" circular reference chapter 6

Good dongdong, I also bottom,