Hi all,
Even i have problems when i call sipxunintialize or
SipxReInitialize ( which in turn calls SipxUnInitialize) , i traced down
this error to void OsSocket::close() which is called while ~SipUserAgent()
is called. I could not find why it crashes at this point. Another strange
behaviour is that this SipxUnitialize is working fine when i run my code
from the IDE , Visual studio or Borland. Anyone has encountered this problem
before ?
-Best,
Amith
On Dec 14, 2007 1:21 PM, li zhang <[EMAIL PROTECTED]> wrote:
> Thanks your reply, but I wonder that why the dialog test never crash.
> The dialog loads the same ocx control as IE that used sipxtapi.
> Can you contribute your test code? Probably, the reason will be found
> by one person.
>
> 2007/11/30, Sargrad, Dave <[EMAIL PROTECTED]>:
> >
> > I dont think this is a problem between sipxtapi and IE. I do think it
> > is a problem with trying to run sipxtapi in a mulit-threaded application. I
> > also see a shutdown crash in my multi-threaded application (which does not
> > use IE). I believe that it is a problem in the non-synchronized shutdown of
> > threads within the application (the sipxtapi thread in particular). In fact
> > I was able to do some simple tests in which I only do a sipxtapiinitialize
> > followed by a sipxtapiunintialize in my threaded application and i see
> > crashes.
> >
> > In general I use a lot of threads in my application and dont have any
> > trouble shutting down the application except when I plugin the thread that
> > uses sipxtapi. Since I build from source code I did take the time back in
> > the summer to try to isolate this long-standing problem. I got down in the
> > guts of sipxtapi, but didnt succeed in fully isolating this.
> >
> > Does anyone else use sipxtapi in multit-threaded applications?
> >
> >
> > ------------------------------
> > *From:* li zhang [mailto:[EMAIL PROTECTED]
> > *Sent:* Thursday, November 29, 2007 3:43 AM
> > *To:* [email protected]
> > *Subject:* [sipxtapi-dev] Fwd: Help on system crash issue when using
> > sipxtapiin IE!!!
> >
> > Hi,all. There is a strange problem in my program using sipxtapi. I
> > build a ocx control with sipxtapi which is loaded by IE. But when i close
> > IE, system occasionally will blue screen and restart.
> > I have tested it from three phase as follow:
> > 1. I create a new ocx project which just loads sipxtapi and adds two
> > method,one call sipxinitialize() and another call sipxuninitialize().
> > Sipxinitialize() method will be called when IE is opened and
> > sipxuninitialize() method is called before IE is closed. Unfortunately,
> > error occasionaly still occur.
> > 2. I rebuild the same ocx project, not loading sipxtapi, reloaded by
> > IE. According to expectation, crash not occur.
> > 3. Then, I create a new simple dialog project which samely load sipxtapi
> > and call sipxtinitialize() and sipxuninitialize() when dialog is opened and
> > closed. Strangely, error never occur by thousand of tests.
> > So, i guess sipxtapi is confilict with IE. But i do not know why.
> >
> > Below is system dump file:
> > PAGE_FAULT_IN_NONPAGED_AREA (50)
> > Invalid system memory was referenced. This cannot be protected by
> > try-except,
> > it must be protected by a Probe. Typically the address is just plain
> > bad or it
> > is pointing at freed memory.
> > Arguments:
> > Arg1: bad0b148, memory referenced.
> > Arg2: 00000000, value 0 = read operation, 1 = write operation.
> > Arg3: 805648e3, If non-zero, the instruction address which referenced
> > the bad memory
> > address.
> > Arg4: 00000000, (reserved)
> >
> > Debugging Details:
> > ------------------
> > READ_ADDRESS: bad0b148
> >
> > FAULTING_IP:
> > nt!ObpRemoveObjectRoutine+cb
> > 805648e3 833800 cmp dword ptr [eax],0
> >
> > MM_INTERNAL_CODE: 0
> >
> > DEFAULT_BUCKET_ID: DRIVER_FAULT
> >
> > BUGCHECK_STR: 0x50
> >
> > PROCESS_NAME: System
> >
> > TRAP_FRAME: f7b41cdc -- (.trap 0xfffffffff7b41cdc)
> > ErrCode = 00000000
> > eax=bad0b148 ebx=00000000 ecx=00000000 edx=822f5060 esi=822f5070
> > edi=00000000
> > eip=805648e3 esp=f7b41d50 ebp=f7b41d60 iopl=0 nv up ei ng nz na
> > pe nc
> > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> > efl=00010286
> > nt!ObpRemoveObjectRoutine+0xcb:
> > 805648e3 833800 cmp dword ptr [eax],0
> > ds:0023:bad0b148=????????
> > Resetting default scope
> >
> > LAST_CONTROL_TRANSFER: from 80524f44 to 8053431e
> >
> > STACK_TEXT:
> > f7b41c78 80524f44 00000050 bad0b148 00000000 nt!KeBugCheckEx+0x1b
> > f7b41cc4 804e2718 00000000 bad0b148 00000000 nt!MmAccessFault+0x6f5
> > f7b41cc4 805648e3 00000000 bad0b148 00000000 nt!KiTrap0E+0xcc
> > f7b41d60 805737f6 822f5088 00000001 80560ba0
> > nt!ObpRemoveObjectRoutine+0xcb
> > f7b41d74 804e526b 00000000 00000000 82fb8b30
> > nt!ObpProcessRemoveObjectQueue+0x38
> > f7b41dac 8057ce15 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
> > f7b41ddc 804fb4da 804e5196 00000000 00000000
> > nt!PspSystemThreadStartup+0x34
> > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
> >
> >
> > STACK_COMMAND: kb
> >
> > FOLLOWUP_IP:
> > nt!ObpRemoveObjectRoutine+cb
> > 805648e3 833800 cmp dword ptr [eax],0
> >
> > SYMBOL_STACK_INDEX: 3
> >
> > SYMBOL_NAME: nt!ObpRemoveObjectRoutine+cb
> >
> > FOLLOWUP_NAME: MachineOwner
> >
> > MODULE_NAME: nt
> >
> > IMAGE_NAME: ntoskrnl.exe
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
> >
> > FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObpRemoveObjectRoutine+cb
> >
> > BUCKET_ID: 0x50_BADMEMREF_nt!ObpRemoveObjectRoutine+cb
> >
> > Followup: MachineOwner
> >
> > Anybody know the reason? I would greatly appreciate you for giving any
> > idea.
> >
> > LiZhang
> >
> >
> >
>
> _______________________________________________
> sipxtapi-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
>
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
