Window exception error after exiting dialog

[cwsoft]

I am a new user to GDPicture Pro SDK with Alaska Sofware's Xbase++ software. I had previously use a different vendors TIFF image viewer and image software. The software is working fine. However, when I exit the viewer dialog, and continue working in the rest of the application, the application generate a standard windows application error (GPF). If i leave the GD picture viewer dialog running and do not close it, the application runs all day without a problem. However, when I close it, the application will error out spontaneously, even when not actively in the application within a short period of time.

Thus, it appears that I am not shutting down the viewer properly. I did not have any similar problem with the other ActiveX viewer software. Is there something special I need to do to properly release resources, etc. I tried doing an oTifView:closeimage() immediately prior to closing the dialog, but that did not help at all.

This problem is preventing me from implementing the GDPicture software.

Environment is WinXP. Occurs on several different machines.

Thanks.

Cliff.

[cwsoft]

In addition, this is the error information I received:

Windows standard application error screen:

MAINSL1.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.

One time received the following memory access message:

GDI+ Window: MAINSL1.EXE - Application Error

The instruction at "0x088a730c" referenced memory at "0x088a730c". The memory could not be "read". Click on OK to terminate the program. Click on CANCEL to debug the program.

It appears that when I exit the dialog, not everything is being released/cleared out properly. After about 10 minutes, when remaining in the rest of the application, the error happens EVERY time.

Cliff.

[cwsoft]

In addition, this is a multithreaded application. The viewer is started in its own thread and the thread terminates when it is restarted again. It the library not thread safe????


Cliff.

[Loïc]

Hi Cliff,

Unfortunately it is impossible for out team to help you because we have neither license and knowledge of xbase++

I can only suggest you to check if you are using the latest release which include several bug fixes about application crash on GdPicture Object release.

Also, you can try to call the Terminate method of the GdViewer control within your thread finalization.

With best regards,

Loïc

[cwsoft]

Thanks for the info. It is likely that the terminate option would be the cause. I will test this. It terminate the only method to use to cause make the activeX control remove from memory. If I also use the imaging control, do I also need to make certain that is terminated.

As for the version, it was what was downloaded last week. 5.xx.11.

[cwsoft]

I did test using the :terminate() method prior to closing the thread. This does appear to have cleared up the problem. I missed it in the original review of the methods available.

Thanks for the assistance.

Cliff.

[cwsoft]

I would like to update this. Using the terminate() method appeared to solve the problem only if I exited the dialog a single time. If I called the viewer process again, then did the same termination using the terminate() method, it would then very shortly have a memory access problem.

I know you don't know nor have access to Xbase++.

Could you provide me a simple VB6 code fragment that does the following.

From a main application menu
1 Create a viewer control in its own thread
2. Read in and display a TIFF
3. Close the dialog back, including proper usage of the :terminate() method
4. You return back to the main application menu after closing the thread()
5. Start the process at 1 again.

It appears that in someway I am not closing and releasing the control properly. I can get it to work if instead of exiting the control and attempting to release it, I just hide the control and when called again, just unhide it. I then only exit the control if the entire application is exited.

What is the proper way to close a previously opened dialog with the viewer control being used.

Cliff.

[Loïc]

Hi Cliff,

Writting a new vb6 sample is not useful at all. The Terminate function have no behavior under vb6 and should be used only to fix some thread termination issues from some development environment (IE: old Real Basic editions).

I am quite sure that the problem come from your environment of development which seems to have some trouble to release from memory third party components.
I already got this same problem with Dbase plus and the resulting was DBase Plus license acquisition for me, language learning + 1 month of investigation to find a bug from dbase Plus. The bug has been solved bu the Dbase team without any "thank you' or something else...

What I can suggest you is to write a very simple application which reproduce the behavior and send it both to esupport (at) gdpicture (dot) com & to the xbase support. If we are able to get free license from they we will have a look on your project.

Kind regards,

Loïc

[cwsoft]

I am working on just such a simple application for testing with Xbase++ support from Alaska Software. Depending on what they find, they are more than willing to work with you to resolve the problem, especially if it is something in the Xbase++ software.

I will keep you posted.

In the mean time, I have modified my application to keep the GD Picture Pro thread open permanentaly once opened and only close the thread when the application is closed. It appears to work in this fashion.

Cliff.