#1248 Windows error: Open Object Rexx Interface has stopped working

None
open
nobody
None
None
1
2014-03-10
2014-02-19
Jeff
No

I and several users are facing this bug very often with 2 different programs I wrote.

The Symptom is a Windows error panel: "Open Object Rexx Interface has stopped working".

As far I can remember, it never occured on Windows xp. It started to surface since we upgraded to Windows 7 64-Bit.

Despite it occurs with all versions from 4.1.0 to 4.1.2, it looks to be more frequent on ooRexx 4.1.3 (containing oodialog 4.2.2).
Problem is still present with ooRexx 4.2.0 and ooDialog 4.2.3.

Note that we are running the 32bit versions of ooRexx/oodialog because programs are accessing the IBM Personal communication sessions using EHLAPI32.dll which is 32bit only.

It randomly occurs at different program steps. There are no Rexx errors of any kind.
It seems to me that it depends on the memory consumption (program fails after having run several times the program method).

At Failure time, the command line shows: > Terminated with exit code -1073741819 with the Windows message: "Open Object Rexx Interface has stopped working".

From the windows problem details panel (Control Panel\System and Security\Action Center\Problem Details) here is the Description:

With REXXHIDE.EXE:
Faulting application name: REXXHIDE.exe, version: 4.1.3.9341, time stamp: 0x51d621ae
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb1072
Exception code: 0xc0000005
Fault offset: 0x0002e3be
Faulting process id: 0x29cc
Faulting application start time: 0x01cefedf245b6f78
Faulting application path: C:\PROGRAM FILES (X86)\OOREXX\REXXHIDE.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b81e468d-6adb-11e3-a67d-0021cc61b3e8

With REXX.EXE
Faulting application name: rexx.exe, version: 4.1.3.9341, time stamp: 0x51d621ad
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb1072
Exception code: 0xc0000005
Fault offset: 0x0002e426
Faulting process id: 0x462c
Faulting application start time: 0x01ceede604b31735
Faulting application path: C:\Program Files (x86)\ooRexx\rexx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 593647fa-59d9-11e3-9f7f-0021cc61b3e8

With REXXHIDE.EXE and ooRexx 4.1.2 (faulting module is different but symptom is the same)
Faulting application name: REXXHIDE.exe, version: 4.1.2.8305, time stamp: 0x503d7f0a
Faulting module name: rexx.dll, version: 4.1.2.8305, time stamp: 0x503d7eff
Exception code: 0xc0000005
Fault offset: 0x000644e5
Faulting process id: 0xc68
Faulting application start time: 0x01cefe112dd1326e
Faulting application path: C:\Program Files (x86)\ooRexx\REXXHIDE.exe
Faulting module path: C:\Program Files (x86)\ooRexx\rexx.dll
Report Id: da4d2776-6a28-11e3-a381-001e3746a47e

Because of the professional environment the programs are running on, it would be difficult to provide a sample to reproduce the problem.

Can you take a look at this and tell me what I could do to help you to fix this problem, what type of information I can provide.

Thanks for your help.

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2014-02-19

    The Windows 7 message of Open Object Rexx interface has stopped working just means the program crashed.

    Since you mention the version of ooDialog and are using rexxhide at least some of the time, I assume your program is using ooDialog. The crash could be caused by ooDialog, or the crash could come from the interpreter.

    Unfortunately there is no way to tell from the information you have.

    Without an example program that produces the crash, there is really not much we can do. If you can not produce a small example that crashes, what about making the program itself and the steps to recreate the crash available?

     
  • Jeff
    Jeff
    2014-02-19

    Yes, the programs are using oodialog.
    I already spent some times to isolate the problem and to create an example, but it was not successful.
    I will try anyway to find a way to provide you an example.

     
  • Mark Miesfeld
    Mark Miesfeld
    2014-02-20

    Hi Jeff,

    We have decided to make a debug build of the Windows version of the interpreter available.

    If, and only if, you a VC++ debugger installed on your system, running your program with the debug build may give some extra information that could help track down the problem. Provided that your program crashes under the debug version of the interpreter.

    You can get the debug build for 4.2.0 from a subdirectory of the ooRexx 4.2.0 Files section on SourceForge:

    https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%202%29/debug.version/

    This is most likely to help if you have a regular version of Visual Studio or Visual C++ installed. In that case, you can just run your program as normal. If your program crashes, the just in time debugger will break in and you can collect some information for us.

    The regular versions are relatively expensive and it is unlikely you have one of them. If you do good. If you don't, then you could install one of the free "express" versions. We think you should be able to collect the extra information using an express version, but it may be a little more work. It would be best to install a 2010 version, which is the version that ooRexx was built with. You could get Visual C++ 2010 from this URL:

    http://www.visualstudio.com/en-us/downloads#d-2010-express

    Essentially what we would like you to do is collect the stack trace shown in the debugger when your program crashes. This of course involves a bit of work on your part.

    If you don't have a debugger installed and are not going to install one, there is no point in writing a lengthy note explaining how to collect the stack trace. On the other hand, if you intend to try to get a stack trace, just let us know and we'll give you more details. The details depend on if you have the regular debugger, or the express version.

     
  • Jeff
    Jeff
    2014-02-22

    Hi Mark,

    Thanks for efforts you make to investigate this problem.

    As I don't have a regular version of Visual Studio or Visual C++, I installed the Visual C++ 2010 Express Edition.
    I also installed the ooRexx debug version.

    I am ready to follow your instructions on how to collect a stack trace.
    Note: I will be able to do it but not before 2 weeks.

     
  • Jeff
    Jeff
    2014-02-22

    I must to let you know that I am using the Rexx EEC EECEncrypt and EECDecrypt functions with one of the 2 programs (http://rexxeec.sourceforge.net/).

    It was not able to reproduce the problem when this program is not using these EEC functions.

    The other program is not using EEC functions. But it fails with the same symptom, on a less frequent manner. I am not able to trigger the failure.

    Also I am wondering if the first program (with EEC) may impacting the second one.

    I don't want you to spend time on this issue as you are not responsible of the EEC Functions package.

    I will try to find another way to encrypt the data.

     
  • Jeff
    Jeff
    2014-03-10

    I submitted this problem in Rexx/EEC Ticket #1.
    waiting for the outcome.

     


Anonymous


Cancel   Add attachments