Kbase P100500: WebSpeed GPFs when running a program that contains more than 500 fields
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/9/2009 |
|
Status: Verified
SYMPTOM(s):
WebSpeed GPFs when running a program that contains more than 500 fields
Progress WebSpeed generates a GPF (General Page Fault) on the System
Using an HTML mapped program that contains more than 500 input text fields
The following error message appears on the screen:
message title => _progres.exe - Application Error
message description => The instruction at "some-memory-address" referenced memory at "some-memory-address". The memory could not be "read".
Stack trace from _progres reads:
getHandle
umDITEMtoUIC
rnFindEopUIC
rnFindUIC
rnwdatr
fmEWDAX
fmeval
fmeval
fmeval
Using OpenEdge 10.0B the same code fails to compile with error 3307
<segment-name> has exceeded its limit of <segment-size> bytes, in <file-name> at line # <line-number>. (3307)
A Frame Segment has exceeded its limit of 32767 bytes, in at line # 3503. (3307)
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1E
OpenEdge 10.0B
CAUSE:
Bug# OE00111542
CAUSE:
This problem is happening in the laying out a frame. Because the frame contains too many fields and Progress end up overflowing a variable internally which causes to go through the wrong code path, leading to the crash.
FIX:
Upgrade to Porgress 9.1E01 or OpenEdge 10.1A or later.
To workaround this issue review the code and look for unnecessary command like SKIP or SPACE.