Why does the memory rise rapidly when I use a bitmap as a mouse cursor?

Question

0.00/5 (No votes)

See more:

When I use a bitmap as a mouse cursor ,the memory is rising rapidly .I donot know why,but I have dispose it.The code below :
The codes is running to response to the mousemove event.

C#

bmpCursor = global::XRF.Properties.Resources.Cross3;
Graphics g = Graphics.FromImage(bmpCursor);
Brush brush = new SolidBrush(Color.Black);

g.DrawString( (int)pf.X+"\r\n"+pf.Y, new Font(FontFamily.GenericSansSerif, 80f), brush, new PointF(0f, 0f));

//pictureBox1.Cursor.Dispose();
IntPtr hIcon = bmpCursor.GetHicon();
pictureBox1.Cursor = new Cursor(hIcon);//change the cursor of picturebox1 when moving mouse

brush.Dispose();
g.Dispose();

Posted 8-Sep-14 15:54pm

codeprojectddx

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2014-09-08T17:16:00

If you're looking at Task Manager to tell you how much memory your app is using, it's lying to you. It has no idea what the .NET Framework is or how it works. It's showing you how much memory is RESERVED by the .NET CLR for your app.

There's all kind of documentation on the web about this and I'm not going to type it all up again for the 1,000th time.

Now, in your MouseMove event, why are you constantly creating new Graphics and Brushes on every event? Don't. Create them ONCE, when you need to create them and then Dispose of them when you don't need them any more. Doing it on every MouseMove event is just ridiculous as you're creating and destroying the objects in rapid succession, thereby driving up the memory that your app APPEARS to be using.

bling · Answer 2 · 2014-09-12T07:26:00

Don't do this on the Move event. Do so on the Mouse Enter event (and undo it on the Mouse Leave event).

If the particular widget doesn't provide mouse enter/leave events, add them.

If you're stuck using mouse move event, do as Dave suggests but also check to see if the cursor has already been assigned. If the cursor is already set, you don't need to set it again.

Why does the memory rise rapidly when I use a bitmap as a mouse cursor?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0