I think the reason may be the architectural problem (only one INST) mentioned in a couple of threads (eg. viewtopic.php?f=66&t=28922&p=112186&hil ... ce#p112186 or viewtopic.php?f=66&t=25069&p=98153&hili ... ent#p98153).
We create a new SWT Controll site like this:
Code: Select all
new OleControlSite(oleFrame, SWT.NONE, "PDFXEdit.PXV_Control.1")
Because of the hundreds of Documents opened every day we have no chance to keep all this frames/Windows open.
Question is the a solution for the Problem? How do other ActiveX-Application solve this Problem?
Here is a Part of the crash stacktrace:
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 ExceptionCode=c0000005 ExceptionAddress=26E21453 ContextFlags=0001007f
Handler1=6ACE99C0 Handler2=6F729060 InaccessibleReadAddress=03BD63B4
EDI=0000EAC4 ESI=03BD63AC EAX=00000000 EBX=00360000
ECX=00002C84 EDX=251D96A4
EIP=26E21453 ESP=0060F78C EBP=0060F7C8 EFLAGS=00010207
GS=002B FS=0053 ES=002B DS=002B
Module=C:\Program Files (x86)\Tracker Software\Editor SDK\Bin\PDFXEditCore.x86.dll
Module_base_address=26DF0000 Offset_in_DLL=00031453
Target=2_90_20180425_385365 (Windows 7 6.1 build 7601 Service Pack 1)
CPU=x86 (8 logical CPUs) (0x3fa78c000 RAM)
----------- Stack Backtrace -----------
DllUnregisterServer+0x28a3 (0x26E21453 [PDFXEditCore.x86+0x31453])
PXV_GetInstance+0x11e3d (0x26E52D7D [PDFXEditCore.x86+0x62d7d])
(0x3E99A13B)
(0xD8375C20)
(0x76F78475)
(0x124E3992)
(0xFC6859E8)