Patch Number

Ticket Number

Change type



Enhancement and Patch

1. Description

This change improves the handling of mutexes in jBASE.

2. Previous Release Behavior

The problems were usually seen on a Windows platform. They could have occurred on other platforms, but would have failed silently. For now we'll concentrate on Windows.

Various Mutex errors were reported. Timeout messages were common, as well as MutexLock: Error: Result nn, Error 0 error messages.

The timeout messages sometimes have details of the position in the jBASE run-time, and this was often when doing a mallinfo() call to obtain memory allocation information.

A lot of the mutex error problems seem to point to the jBASE listening thread interacting with the main thread.

3. Current Release Behavior

While it is not certain that all instances of this have been addressed, should a mutex timeout error occur then jBASE will provide additional info as to the nature and source of the error, e.g.

MutexLock: Result nn, Error nn, filename /home/jbasedev/xxx/jbase/blahblahb.c,453

This will would hopefully give us more information on where and why the errors have occurred so that they can be addressed in a future release.

Specifically, the changes that were made are: