Re: Slow to Create RasterSupport object

Hi,
we have a VB6 application using the Latest version of LeadTools 15 through the COM Interop layer

On of our laptops, brand new machine,the call to unlock the support keys is very slow

the lines below take around 24 seconds to execute, in particular the creating of the new RasterSuport object

Dim ltSupport As RasterSupport

Set ltSupport = New RasterSupport

is there anything obvious I could check ?

thanks
Martin

Hello Martin,

Do you see this same issue with our Main VB COM demo?

Do you have any other machines that illustrate this with the same setup, or is it just on this one laptop?

If you disconnect from the internet, does the issue disappear on this laptop? If not, what build version of Leadtools.dll is on this machine?

Hello Walter, thanks for the reply

Disconnecting from the internet doesn't make a dfifference

It happens on two laptops, both of which are new sales demos machines

It doesn't happen with the main VB COM demo which is odd as I've made sure that my little noddy test program has the same references and that the first thing both programs do is create a rastersupport object to unlock some features

I've tried it with a couple of versions of leadtolls.dll
15.0.1.7 and 15.0.1.33

will play around with the demo program and my one to try and see what the diff is but any other suggestions would be appreciated

thanks
martin

Martin,

Since this issue doesn't exist in our main demo then it may be doing something slightly different than you're doing. If you have multiple versions of our dlls on your machine, this could also cause some issue if our demo is loading one set of dll and your application is loading another.

You indicated originally that these brand new machines were having this issue. Do you have nother machine running this same exact code that does not experience this issue? If the code is exactly the same on both machine, but they are executing differently, the common denominator between the two would be the dlls they're executing. Checking these should indicate the problem. A tool like Microsoft's Process Explorer will indicate at runtime what dlls are getting loaded, and where they're getting loaded from.

What operating system are these two laptops running?

If you continue to have difficulties with this, please email a small sample project (not your entire application) which isolates this issue to support@leadtools.com so that I can look into this matter further. Small sample applications are generally one or two button forms that easily illustrate the issue. Also, please include a link to this forum post.

hello Walter, sorry for the delays in getting back to you but we have found a bit of a workaround for it that will suffice so just for your info

The Demo program creates instances of Lead objects, Support, RasterImage, RasterCodecs, DocumentEngine straight away on the main MDI form and that must be keeping something in memory that the other LEAD interop stuff looks for - we weren't creating any LEAD objects or calling support in out main MDI form, instead t was being created when a menu option created an instance of out wrapper class that encapsulates all the LEAD stuff, including the support which was taking 20 to 30 seconds to load up - any ways we found a work around by putting references to the LEAD objects on out MDI form and delay went away

Thank you for the information. It will help others who are experiencing this same issue.