Freeze/GPF When Calling Find and Replace (RTF)

All,

Having an issue with a Clarion 10 application where calling a Find and Replace dialog freezes and very occasionally GPFs an application after performing the replace action. This only seems to occur on Windows 7, cannot replicate using same exact application/assemblies on Windows 10 (haven’t tested on 8/8.1). This is simply calling the standard Windows find & replace dialog.

Program : \APPPATH\ATS.exe
Version :
At : 14:41:39 on 2018/02/02
Workstation: : Training-PC2
User Name: : Administrator
Reported error : EXCEPTION_ILLEGAL_INSTRUCTION
: Flags=00000000 Except2=00000000
Windows : Win 7 , Terminal Server - 6.1.7601 Service Pack 1
Clarion : 0.9
Thread : 6 Field : 12 Event : 1 Keycode : 1
Error at address : 6DC11EF2h no debug info, Module=C:\Windows\system32\Msftedit.DLL 5.41.21.2510
Stack Trace
[01] 6DC33C0Fh no debug info, Module=C:\Windows\system32\Msftedit.DLL 5.41.21.2510
??? 01FFCB34h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
[02] 01F796ECh no line number no proc Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 02010DD4h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 00C72599h Line=1560 Proc=RTFFINDANDRELACEDLG@Fsbsb Src=RTFCTL.CLW Module=\APPPATH\ATSGLO.dll 5.0.0.0
??? 01FADA90h Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FABA61h Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FAB5A1h Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FA8E45h Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FA8EAFh Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 00C722AFh Line=1517 Proc=RTFFINDANDRELACEDLG@Fsbsb Src=RTFCTL.CLW Module=\APPPATH\ATSGLO.dll 5.0.0.0
??? 01FE94E8h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FCD3EAh Line ?=27 no proc Src=“Library State” Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 00C72799h Line=1588 Proc=RTFFINDANDRELACEDLG@Fsbsb Src=RTFCTL.CLW Module=\APPPATH\ATSGLO.dll 5.0.0.0
??? 02008C03h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 00497E40h Line ?=51 no proc Src=VSA_TERM.CLW
??? 01000000h Line ?=446 no proc Src=WinExt.CLW Module=\APPPATH\ATSGLO.dll 5.0.0.0
[03] 01F8F65Bh no line number no proc Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 02008B30h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FE94D2h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
[04] 01F8F145h no line number no proc Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FE94E8h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 02008B30h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 02008BB0h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD158h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD16Ch Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD188h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD17Ch Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD1A4h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
??? 01FFD198h Line ?=47 no proc Src=wxeh.cpp Module=\APPPATH\ClaRUN.dll 10.0.12278
[05] 770D98F2h no debug info, Module=C:\Windows\SysWOW64\ntdll.dll 6.1.7600.16385 (win7_rtm.090713-1255)
[06] 770D98C5h no debug info, Module=C:\Windows\SysWOW64\ntdll.dll 6.1.7600.16385 (win7_rtm.090713-1255)

1 Like

Hey @NimbusHex !

Just to clarify, is this Find & Replace in the Clarion IDE or in your compiled application?

@brahn

This is in a compiled application.

Thanks!

What sort of document are you doing the replace in?
What else are you doing when you call the search and replace? Are you in a form, a browse, ???

All, sorry for the lack of reply lately. As far as I know this is the standard Clarion RTF editor template. We confirmed this issue is isolated to Windows 7, and including a later version of MSFTEdit.dll in our application folder resolved the issue. Hope this helps someone who may be having the same issue.