Re: Memory Leak - Please MVP

Hi.

Maybe You could try to store your large data in a compressed way.(I
don't know if there are some compression libraries for VB cause I'am
using c# in my development). This causes some performance losses for
your application, but maybe it is better than memory leaks. As long as
there are no binary data in your XML it should not be a problem. (I'am
not familiar with the undo functions of visio so this memory leak
problem could still occure. If this solution really helps can only be
figured out through testing...)

Igor Markov
Visio Plugin Developer

Mark Nelson [MS] wrote:
Hi Shahzad,

Visio does not support selectively putting things into the undo stack. If
you are manipulating a Visio object and undo is enabled, then Visio will
record the transaction in undo.

--
Mark Nelson
Office Graphics - Visio
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"Shahzad Godil" <shahzadgodil@xxxxxxxxx> wrote in message
news:e2onWj4jGHA.896@xxxxxxxxxxxxxxxxxxxxxxx

I have now implemented this Visio Undo Manager. But its purpose looking
just to keep our external data and drawing sync on undo and redo. My
purpose is different. What my purpose is that I am not dealing with any
external data. What I want simply is that I want my few drawing actions
should not be add in Undo queue.

For example, in clear words. Here is my procedure doing

1. BeginAction
Shape1 Added
End Action

2. Begin Action
. Shape1.Data1 = "abc" (large text)
End Action

3. Begin Action
Shape2 added
End Action

Now what I want that that Action2 i.e. setting some data in data1 should
not be include in Undo Queue. And whenever I do undo, it should be return
to first Action3 and then Action1 by skipping Action1

Thanks
Shahzad Godil


"JuneTheSecond" <JuneTheSecond@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0175A9DD-7D64-4A72-943B-1D1F68ABD8A1@xxxxxxxxxxxxxxxx
Then, "Chapter 25, Using the Visio Undo Manager in Your Program" might be
a
good reerence, though I feel its tough to me.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/devref/html/DVS_01_Introduction__544.asp

--
JuneTheSecond



"Shahzad Godil" wrote:


I am Architect of development of our one Visio based application in
VB.Net
2003. So many customer continously reporting memory leak issue in our
application. I am using different profiler to find out which area is
getting memory and then verifying that either it is relelasing properly
at
the end of that process.

In going detail, we were able to fix so many issues by implement general
practices for handling Unmanaged code.

Now only one issue is now remaining which is causing memory leak is
this.
If you see this code, we are assigning a very large string to our Data1
property of Visio Shape. And now whenever it is assigning, it is never
releasing.

Now seems like as it is changing, visio is keeping this in its undo
history.

What I want simply is that whenever I called this method, its changes
should
be applied in diagram but it should be include in visio undo history.

Thanks
Shahzad Godil
Karachi-Pakistan.

-----------------------------------------
Dim strString As String

strString = Me.ShapeDomain.GetAsXML.OuterXml

Me.VisioShape.Data1 = strString

strString = Nothing

-------------------------------






.

Relevant Pages

  • Re: visio internal error 2123
    ... you programmatically drop additional shapes. ... You also want to handle undo properly. ... Any change you make to the Visio drawing is automatically ... > 1) We have different kinds of shapes like switches, cables, fabrics. ...
    (microsoft.public.visio.developer)
  • Re: visio internal error 2123
    ... We are programmatically creating undo units. ... parallely which encompasses information about the state of Visio application. ... We have different kinds of shapes like switches, cables, fabrics. ...
    (microsoft.public.visio.developer)
  • Re: visio internal error 2123
    ... Office Graphics - Visio ... > some shapes that were dropped earlier in the similiar fashion.The Undo ... The undo unit observed in the Edit box just after deleting all ...
    (microsoft.public.visio.developer)
  • Memory Leak
    ... I am Architect of development of our one Visio based application in VB.Net ... Now only one issue is now remaining which is causing memory leak is this. ... Now seems like as it is changing, visio is keeping this in its undo history. ... Dim strString As String ...
    (microsoft.public.vsnet.vstools.office)
  • Memory Leak
    ... I am Architect of development of our one Visio based application in VB.Net ... Now only one issue is now remaining which is causing memory leak is this. ... Now seems like as it is changing, visio is keeping this in its undo history. ... Dim strString As String ...
    (microsoft.public.visio.developer)