#41 closed defect (fixed)
Trap in PMMERGE.DLL on starting external program which appears to be caused by estlrl11.dll
Reported by: | Gregg Young | Owned by: | Gregg Young |
---|---|---|---|
Priority: | minor | Milestone: | Release_1.1 |
Component: | Other | Version: | PreRelease_1.0 |
Keywords: | Cc: |
Description
12-15-12 19:23 40,456 0 _A_ estlrl11.dll
Signature: @#AlessandroCantatore:1.1#@eStylerLite V.1.1.96 - (c) 1998-2004
Alessandro Cantatore
Vendor: AlessandroCantatore
Revision: 1.01
File Version: 1.1
Description: eStylerLite V.1.1.96 - (c) 1998-2004 Alessandro Cantatore
Attachments (1)
Change History (9)
by , 9 years ago
Attachment: | 0087_01.TRP added |
---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Milestone: | → Release_1.0 |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:3 by , 9 years ago
Status: | assigned → accepted |
---|---|
Version: | → Release_1.0 |
comment:4 by , 9 years ago
Version: | Release_1.0 → PreRelease_1.0 |
---|
comment:5 by , 8 years ago
Milestone: | Release_1.0 → Release_1.1 |
---|
comment:6 by , 7 years ago
I have this mostly fixed by removing the redundant hide window call in the close code. I now think it has something to do with how eftepm is opened. If I open a file from FM2 using edit it almost never happens but if I open using the FM2 association it happens more often (still very infrequent). I don't think it has happened at all if I open the first file from eftepm itself. Need to see how these differ in FM2.
comment:7 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
This appears to have been caused by the way we were calling WinDestroyWindow
comment:8 by , 4 years ago
This was not a problem with a dialog window. It is a problem with a bubbleHelp window. CS [226] seems to have fixed it.
No pdump file was generated.