Whenever Multiview is used to view any Amigaguide document, when hit close gadget we get a "Recoverable Error" pop-up.
(I have only tested in ApolloOS, so don't know if this is a generic Aros bug that was 'inherited')
Steps to reproduce the behavior:
Go to CLI
Type command "Multiview"
In file selection, choose any AmigaGuide document, such as Programs:Developer/SagaDocs/adkcon.guide
Close window
See error
Expected behavior
The expectation s that the window should close
Screenshots
Configuration
Apollo Device - V4 Stand Alone using ApolloOS R9.4
Additional context
The recoverable error mentions code 0x35000000, which means LAWBREAKER, which only seems to occur when the datatype usage count is unexpectedly 0, then it tries to decrease the usage count in releasedatatype.c
This indicates that the open count was either not properly increment elsewhere when the datatype was used, or counter was subsequently trashed.
I see two possible places where this counter seems it would be increased, so maybe something is bypassing correct flow in one these two routines
workbench/libs/datatypes/lockdatatype.c
workbench/libs/datatypes/obtaindatatypea.c
However, the recoverable alert actually is really just a debug message. And the counters it complains about actually do nothing. Suggest only either removing the alert, or only outputting it debug msg mode is turned on.
Whenever Multiview is used to view any Amigaguide document, when hit close gadget we get a "Recoverable Error" pop-up. (I have only tested in ApolloOS, so don't know if this is a generic Aros bug that was 'inherited')
Steps to reproduce the behavior:
Expected behavior The expectation s that the window should close
Screenshots
Configuration Apollo Device - V4 Stand Alone using ApolloOS R9.4
Additional context The recoverable error mentions code 0x35000000, which means LAWBREAKER, which only seems to occur when the datatype usage count is unexpectedly 0, then it tries to decrease the usage count in releasedatatype.c
This indicates that the open count was either not properly increment elsewhere when the datatype was used, or counter was subsequently trashed.
I see two possible places where this counter seems it would be increased, so maybe something is bypassing correct flow in one these two routines
However, the recoverable alert actually is really just a debug message. And the counters it complains about actually do nothing. Suggest only either removing the alert, or only outputting it debug msg mode is turned on.