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
The returned values usually have %USERPROFILE% keys so to get the full path, we had to first access the environment variable and then substitute it. We got the variable value using:
Smalltalk os environment at: 'USERPROFILE' ifAbsent: ''
And as soon as we started to do it, we got tons of strange errors related to file access to log files we create. We have proven that these errors occur only if we perform the registry access.
So, my next guess was to try to pin intermediate values during the registry access in memory because some strange memory corruption is probably happening.
We had an "interesting" issue. In our case, we needed to access the path to the Documents folder.
The returned values usually have
%USERPROFILE%
keys so to get the full path, we had to first access the environment variable and then substitute it. We got the variable value using:Smalltalk os environment at: 'USERPROFILE' ifAbsent: ''
And as soon as we started to do it, we got tons of strange errors related to file access to log files we create. We have proven that these errors occur only if we perform the registry access.
So, my next guess was to try to pin intermediate values during the registry access in memory because some strange memory corruption is probably happening.
In
WinRegistry class>>#queryValue:fromKey:
in
WinRegistryKey>>#queryValue:fromSubkey:
It was a fully blind guess, but it seems to solve our problems. Not sure if fully. So I'm reporting it for the next discussion.
The text was updated successfully, but these errors were encountered: