You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Log the enabled / disabled state of the traceLogger mutex mechanic
446
451
try
447
452
{
448
-
TL.LogMessage("Environment", $"TraceLogger is {(Utilities.Global.GetBool(USE_TRACELOGGER_MUTEX, USE_TRACELOGGER_MUTEX_DEFAULT) ? "" : "not ")}using the Mutex mechanic");
453
+
TL.LogMessage("Environment", $"TraceLogger is using the {(Utilities.Global.GetBool(USE_TRACELOGGER_MUTEX, USE_TRACELOGGER_MUTEX_DEFAULT) ? "Mutex" : "lock()")} mechanic");
449
454
TL.LogMessage("Environment", $"TraceLogger debug is {(Utilities.Global.GetBool(TRACELOGGER_DEBUG, TRACELOGGER_DEBUG_DEFAULT) ? "enabled" : "disabled")}.");
455
+
TL.LogMessage("Environment", $".NET component use logging is {(Utilities.Global.GetBool(DOTNET35_COMPONENT_USE_LOGGING, DOTNET35_COMPONENT_USE_LOGGING_DEFAULT) ? "enabled" : "disabled")}.");
Copy file name to clipboardExpand all lines: Help/Version History/Version 7.1 Update 2.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,6 @@ here <link xlink:href="7d9253c2-fdfd-4c0d-8225-a96bddb49731#PreReqs70">Platform
16
16
* Alpaca Dynamic Driver log files are now named ASCOM.DynamicDriver... rather than ASCOM.AlpacaSim...
17
17
* Update checker messages now refer to 'Updates' rather than 'Service Packs'.
18
18
19
-
20
19
## Issues Fixed in 7.1 Update 2 - For Everyone
21
20
* Fixed an issue, introduced in Platform 7.1, that caused drivers that use ASCOM COM objects to fail in some environments, including Windows ARM 64bit.
22
21
The issue also caused the 64bit Platform installer validation test to report a -1073741819 error.
Copy file name to clipboardExpand all lines: Help/Version History/Version 7.1 Update 3.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,31 @@ In line with previous Platform installers, Platform 7.1 Update 3 is a cumulative
11
11
Platform releases and service packs. The Platform environment pre-requisites are listed
12
12
here <linkxlink:href="7d9253c2-fdfd-4c0d-8225-a96bddb49731#PreReqs70">Platform Prerequisites</link>.
13
13
14
+
## Changes in 7.1 Update 3 - For Everyone
15
+
* Logging is now more reliable and slightly faster.
16
+
* A new option has been added to the Diagnostics application (`Use TraceLogger mutex synchronisation`) so you can revert to previous
17
+
logging behaviour if necessary.
18
+
14
19
## Issues Fixed in 7.1 Update 3 - For Everyone
15
-
* Fixed - TraceLogger occasionally threw `ProfilePersistenceException - Timed out waiting for TraceLogger mutex` exceptions.
20
+
* Fixed - Widely reported issues where TraceLogger returned `ProfilePersistenceException - Timed out waiting for TraceLogger mutex` exceptions
21
+
causing many clients and drivers to fail. This issue first appeared in Platform 7.1 Update 2.
22
+
23
+
## Changes in 7.1 Update 3 - For Developers
24
+
* The default locking mechanic in TraceLogger has been changed to use an instance local lock() instead of a global mutex.
25
+
* Since its introduction in 2009, TraceLogger has used a global Windows mutex to synchronise writing to log files.
26
+
The impact was that only one log message could be written at a time across all instances of TraceLogger and all applications.
27
+
* The default locking mechanic has been changed to an instance local lock() because this is sufficient to protect the file being written and allows concurrent writing of log files.
28
+
* It is strongly recommended that the new default lock() synchronisation is used as it is faster and does not cause application issues due to mutex timeouts.
29
+
* A new TraceLogger property <codeEntityReferencelinkText="TraceLogger.UseMutexSynchronisation">P:ASCOM.Utilities.TraceLogger.UseMutexSynchronisation</codeEntityReference>
30
+
has been added so the original global mutex synchronisation can be re-enabled if required for use cases where logging synchronisation between processes is required.
31
+
* A new option has been added to the Diagnostics application that enables end-users to revert all ASCOM TraceLogger activity to the original
32
+
global mutex synchronisation without requiring code changes.
33
+
34
+
## Issues Fixed in 7.1 Update 3 - For Developers
35
+
* None
36
+
37
+
## Breaking Changes (For Developers) in Platform 7.1 Update 3
38
+
* None are expected, but developers should be aware of the change to the default locking mechanic in TraceLogger described above.
16
39
17
-
## Changes in 7.1 Update 2
40
+
## Changes in the previous update
18
41
See this link for changes and fixes in <linkxlink:href="Version_7.1.2">Platform 7.1 Update 2</link>.
0 commit comments