#1186 ooRexx/oodialog will either hang or crash from deadlock condition

v4.2.0
closed
Mark Miesfeld
None
complete
1
2014-04-15
2013-07-01
Art Heimsoth
No

Running ooRexx 4.1.3 and ooDialog 4.2.3.9254 on 32 bit. On XP the system will crash, and on Win 7 it gives an error indicating the interpreter quit responding. The problem is due to a deadlock condition due to not using unguarded where needed. The test case is attached. Start and then click on OK - when the popup appears, key in any multiple keys - the second key that is keyed will show the problem.

1 Attachments

Related

Bugs: #1157
Bugs: #1163

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2013-07-05

    Just to be clear here, if your Rexx code causes a deadlock, that is not a bug. It is a problem with the Rexx code that can be fixed by changing the code. That is the case for the "is not responding" message on Windows 7.

    I was more concerned with the crash on XP.

     
  • Mark Miesfeld
    Mark Miesfeld
    2013-07-06

    • labels: ooDialog -->
    • status: open --> pending
    • assigned_to: Mark Miesfeld
     
  • Mark Miesfeld
    Mark Miesfeld
    2013-07-06

    Committed revision 9347. [49347] 4.1 fixes

    This was not really a bug in ooDialog. Rather it was due to a problem that was discovered and fixed in trunk quite some time ago. The fix was never back ported to the 4.1 fixes branch.

    This commit adds the change to the 4.1 fixes branch.

     
  • Mark Miesfeld
    Mark Miesfeld
    2013-12-08

    This is fixed in 4.1 fixes. It was also fixed in trunk a long time ago. Since 4.2.0 will probably be released next, changing the milestone to better track it.

     


Anonymous


Cancel   Add attachments