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
It seems in ApolloOS, that OpenLibrary() and CloseLibrary() invocations of dos.library are unbalanced,
and that the close() method in dos.library is not being reached in many cases.
To Reproduce
-Booted up ApolloOS
-Navigated to Scout, double-click
Click on "Libraries" to show current libraries, and the current open count etc
Expected behavior
Expect a fairly low number of 'currently open' counts (eg 1-50), however see 4335.
Looking at the dos.library source, the counter goes up by one for every Open, and down by one for every close.
To me this indicates that the system thinks that there are 4335 active programs that are still running that have a lock on the dos.library, although only have 52 tasks active.
Eachtime I check, the count seems to go up even higher.
Screenshots
Configuration
Amiga Computer:
Apollo V4 Stand Alone, ApolloOS 9.4.2
Additional context
N/A
The text was updated successfully, but these errors were encountered:
It seems in ApolloOS, that OpenLibrary() and CloseLibrary() invocations of dos.library are unbalanced,
and that the close() method in dos.library is not being reached in many cases.
To Reproduce
-Booted up ApolloOS
-Navigated to Scout, double-click
Click on "Libraries" to show current libraries, and the current open count etc
Expected behavior
Expect a fairly low number of 'currently open' counts (eg 1-50), however see 4335.
Looking at the dos.library source, the counter goes up by one for every Open, and down by one for every close.
To me this indicates that the system thinks that there are 4335 active programs that are still running that have a lock on the dos.library, although only have 52 tasks active.
Eachtime I check, the count seems to go up even higher.
Screenshots

Configuration
Amiga Computer:
Apollo V4 Stand Alone, ApolloOS 9.4.2
Additional context
N/A
The text was updated successfully, but these errors were encountered: