#21 closed defect (invalid)
Exceptq report on shutdown/exit - lSwitcher 2.8.1
Reported by: | Lewis Rosenthal | Owned by: | Gregg Young |
---|---|---|---|
Priority: | major | Milestone: | 2.9.0 |
Component: | standalone | Version: | 2.81 |
Keywords: | Cc: |
Description
Note files attached.
TRP files are created at system shutdown (using XWP Xshutdown) and when manually closing lSwitcher from the context menu.
Also, xshutdwn.log excerpt attached (goes with 0070_02.TRP).
Attachments (8)
Change History (19)
by , 10 years ago
Attachment: | 0070_02.TRP added |
---|
by , 10 years ago
Attachment: | xshutdwn.log added |
---|
Goes with 0070_02.TRP (nothing recorded in xwptrap.log)
follow-up: 2 comment:1 by , 10 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
I am guessing this is with the freestanding version not the xcenter plugin
comment:2 by , 10 years ago
Replying to gyoung:
I am guessing this is with the freestanding version not the xcenter plugin
It is indeed, Gregg.
The issue persists with the latest drop you sent me today:
8-16-14 15:34 69,684 124 lSwitch.exe
TRP attached.
by , 10 years ago
Attachment: | 008E_02.TRP added |
---|
TRP generated upon exit, with 2014-08-16 build of exe
by , 10 years ago
Attachment: | 0041_02.TRP added |
---|
TRP generated upon exit, with 2014-08-17 build of exe
by , 10 years ago
Attachment: | 0086_02.TRP added |
---|
TRP generated upon exit, with 2014-08-17 build of exe (test 3)
comment:4 by , 10 years ago
Per the attachment, test 3 also traps on exit:
Failing Instruction ______________________________________________________________________ 00027B23 PUSH 0xa (6a 0a) 00027B25 MOV EAX, [EDI+0x790] (8b87 90070000) 00027B2B PUSH EAX (50) 00027B2C CALL 0x1ffc08e0 (e8 af8df91f) 00027B31 >ADD ESP, 0x8 (83c4 08) 00027B34 CMP EAX, 0x280 (3d 80020000) 00027B39 JNZ 0x27d47 (0f85 08020000) 00027B3F PUSH 0xc8 (68 c8000000) ______________________________________________________________________ Registers ______________________________________________________________________ EAX : 0000005F EBX : 00000000 ECX : 80010101 EDX : 80010101 ESI : 00725EB4 EDI : 18DD0000 ESP : 00725E68 EBP : 00725EBC EIP : 00027B31 EFLG : 00002246 CS : 005B CSLIM: FFFFFFFF SS : 0053 SSLIM: FFFFFFFF EAX : not a valid address EBX : not a valid address ECX : not a valid address EDX : not a valid address ESI : read/write memory on this thread's stack EDI : read/write memory allocated by LSWITCH ______________________________________________________________________ Stack Info for Thread 02 ______________________________________________________________________ Size Base ESP Max Top 00006000 00726000 -> 00725E68 -> 00724000 -> 00720000 ______________________________________________________________________ Call Stack ______________________________________________________________________ EBP Address Module Obj:Offset Nearest Public Symbol -------- --------- -------- ------------- ----------------------- Trap -> 00027B31 LSWITCH 0002:00007B31 between FSMonDispat + C1 and ItemNumFromLineNum - 25F 00725EBC 00054940 LSWITCH 0003:00014940 SymDef16/32 read error - 1000 bytes at 17da 00725FE8 00000000 Invalid address: 00000000 ______________________________________________________________________ Labels on the Stack ______________________________________________________________________ ESP Address Module Obj:Offset Nearest Public Symbol -------- --------- -------- ------------- ----------------------- 00725ED8 00033916 LSWITCH 0002:00013916 between _init_threadstksize + 96 and _CBeginThread - 1A 00725FDC 00020202 LSWITCH 0002:00000202 between InitSettings + E2 and LoadSettings - 14E 00725FE0 00020202 LSWITCH 0002:00000202 between InitSettings + E2 and LoadSettings - 14E 00725FE4 00027A70 LSWITCH 0002:00007A70 FSMonDispat 00725FF8 1FFEC188 DOSCALL1 0004:0000C188 between GLOBALINIT + 70 and SGCBINIT - 14
comment:5 by , 10 years ago
Is this on shutdown or from using Quit on the menu? It makes no sense as I am killing the thread that traps in CMD_QUIT. I guess I need to see if something different is trapping than earlier as opposed to my code changes simply moving the error address slightly.
comment:6 by , 10 years ago
This is from Quit on the program (taskbar) context menu (program shutdown, not system shutdown - though during system shutdown, we do get the same report if lSwitcher hasn't been closed previously).
by , 10 years ago
Attachment: | PMPRINTF.LOG added |
---|
pmprintf log 2014-08-17 21:16 build (lswitch sticky window fix)
comment:8 by , 10 years ago
Lewis
These don't appear to be a matched set the trap is from 11:46 Sunday evening but the log is from 00:57 Monday morning. If possible a matched set that shows the lag between the thread being killed and the trap might be helpful. Thanks
Gregg
by , 10 years ago
Attachment: | 008E_02.2.TRP added |
---|
TRP generated upon exit, with 2014-08-17 21:16 build (lswitch sticky window fix)
comment:9 by , 10 years ago
Actually, Exceptq has a habit of appending to an existing TRP file instead of overwriting. The matching info was in the second half of that file (I was trying to figure out why the timestamp in the filesystem didn't match what we were seeing at the top of the file!).
Meanwhile, I've lopped off the old stuff, deleted the initial attachment, and reattached (after much fanfare - LOL). I also have my admin privs working in SeaMonkey (had a stuck cookie, an obvious choking hazard). ;-)
comment:10 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Reporter indicated that trap was caused by exceptq settings
TRP generated upon shutdown.