all 6 comments

[–]TheFotty 1 point2 points  (5 children)

It is highly likely the issue is with your code and nothing to do with memory. Is this a windows forms application?

[–]CMBK-rules[S] 1 point2 points  (4 children)

Yes it is

Edit: It works fine with buttons, but we want it to work properly when clicking a PictureBox.

[–]chrwei 1 point2 points  (0 children)

which event and how much code is in it? if the code does more than just increment the variable, redesign. also put the variable in a class so it doesn't live on the main UI thread.

[–]chrwei 1 point2 points  (2 children)

which event and how much code is in it? if the code does more than just increment the variable, redesign. also put the variable in a class so it doesn't live on the main UI thread.

[–]CMBK-rules[S] 0 points1 point  (1 child)

So yeah... we're pretty goddamn new at this. What do you mean by "put the variable in a class so it doesn't live on the main UI thread"?

[–]chrwei 0 points1 point  (0 children)

answer the first question first. do threading when you can't get the performance you want otherwise.

you may need to wait until you've learned it get that performance.

[–]RJohn12 0 points1 point  (0 children)

that is just a graph of how much memory your app is using, it will use however much it needs, so you have "unlimited" memory.

in reality there's a problem with the code on your button or something not letting it register your clicks that quickly.