Hi,

I have a weird issue with uniface 9.6. 

When I try run a form for a particular record, Uniface crashes out ( Uniface 9 has stopped working). 

But... when I run the same form with the same record in debug mode, I works fine.

Has anyone seen this before?  What could be the cause./solution 

Thanks for your help.

Stanley

Hi,

I have a weird issue with uniface 9.6. 

When I try run a form for a particular record, Uniface crashes out ( Uniface 9 has stopped working). 

But... when I run the same form with the same record in debug mode, I works fine.

Has anyone seen this before?  What could be the cause./solution 

Thanks for your help.

Stanley

Hi,

I have a weird issue with uniface 9.6. 

When I try run a form for a particular record, Uniface crashes out ( Uniface 9 has stopped working). 

But... when I run the same form with the same record in debug mode, I works fine.

Has anyone seen this before?  What could be the cause./solution 

Thanks for your help.

Stanley

Hi Stanley,

based on your rough description it is difficult to provide you with an answer. In your case some memory overwriting seems it is happening...

However, based on my experience, two could probably be reasons for the anomaly:
1 - A single component NOT compiled after an "Application Model" update
2 - A field containing dirty data, probably inserted/updated from outside Uniface, not with a Uniface component based on its "Application Model"

Trying to solve:
1 - Re-Compile and put in use ALL your Uniface components/object...
2 - As already proposed from Iain turn trace trace on entering the faulty component and discover in your log file which is last executed instruction; your issue could be generated from that last instruction or the following one...

Hope it helps! Let us know how you solved...

Regards,
Gianni

Hi,

I have a weird issue with uniface 9.6. 

When I try run a form for a particular record, Uniface crashes out ( Uniface 9 has stopped working). 

But... when I run the same form with the same record in debug mode, I works fine.

Has anyone seen this before?  What could be the cause./solution 

Thanks for your help.

Stanley

Stanley

It is possible to log your proc script execution with following assignment file settings. 

[settings]
$PROC_TRACING = 1
$PROC_LOG_FILE = <FileName>

Additionally you can use the $PUTMESS_LOG_FILE to get all putmess calls and system errors in the log file. In case of a crash it is even possible to have the log lines written directly to disk, however this will cause a serious performance degradation of the application since uniface needs to wait for the physical disk I/O. So do not  use the bold marked setting in production.

$PROC_LOG_FILE = <FileName>, direct

I hope this helps you in finding the issue and solve it.

Regards

Jasper de Keijzer

Principal Software engineer at RocketSoftware.