Wrong reference count keeps showing up in Repair: Difference between revisions
No edit summary |
No edit summary |
||
Line 69: | Line 69: | ||
If you happen to do error checks in short succession and see the error, you may have better hypothesis on how this occurs. Thank you. | If you happen to do error checks in short succession and see the error, you may have better hypothesis on how this occurs. Thank you. | ||
See also: [[Wrong reference count for Text]] | |||
}} | }} |
Revision as of 19:32, 6 March 2018
From: WojtekTM
Country: Poland
Sent: 6th March, 2018
Subject: Persistent errors in collection
Question:
For the long time my SM17 persistently shows the same errors on every repair. If I perform two subsequent repairs, the second one shows no error, however the next day, the same errors appear again. Should I ignore them? Maybe they should be renamed to warnings if they do not affect spaced repetitions process?
++++++++++++++++++++++ ERROR #1 ++++++++++++++++++++++ Wrong reference count for Text #5961: http://localhost/KubernetesUpAndRunning/index.html Count: reported=225 found=224 Registry: text ++++++++++++++++++++++ ERROR #2 ++++++++++++++++++++++ Wrong length of registry usership list for Text #5961: http://localhost/KubernetesUpAndRunning/index.html Count: reported=225 found=224 Registry: text ++++++++++++++++++++++ ERROR #3 ++++++++++++++++++++++ Wrong reference count for Text #8054: Web import Count: reported=1374 found=1373 Registry: text ++++++++++++++++++++++ ERROR #4 ++++++++++++++++++++++ Wrong length of registry usership list for Text #8054: Web import Count: reported=1374 found=1373 Registry: text Warning! Registry member not used Text #11276: To determine the index number or name value image in WIM file use:. dism /get-imageinfo /imagefile:x:\imgagefilename ++++++++++++++++++++++ ERROR #5 ++++++++++++++++++++++ Wrong reference count for Text #11528: Kubernetes: Up and Running: Dive into the Future of Infrastructure Count: reported=212 found=211 Registry: text ++++++++++++++++++++++ ERROR #6 ++++++++++++++++++++++ Wrong length of registry usership list for Text #11528: Kubernetes: Up and Running: Dive into the Future of Infrastructure Count: reported=212 found=211 Registry: text Warning! Registry member not used Text #12417: http://localhost/dockerupandrunning/Images/image00239.jpeg Warning! Registry member not used Text #12837: Imported on Dec 06, 2017, 20:35:53 Warning! Registry member not used Text #13143: A Value Object represents a simple entity (object) whose equality is not based on identity: i.e. two value objects are equal when they have the same value, not necessarily ... Warning! Registry member not used Text #13226: You can also use the /Get-DriverInfo option to display detailed information about a specific driver:. dism /image:c:\mount /get-driverinfo /driver:c:\drivers\driver.inf Warning! Registry member not used Text #13447: image00240.jpeg Warning! Registry member not used Text #13485: image00239.jpeg ++++++++++++++++++++++ ERROR #7 ++++++++++++++++++++++ Wrong reference count for Text #13592: Imported on Dec 08, 2017, 23:51:23 Count: reported=212 found=211 Registry: text ++++++++++++++++++++++ ERROR #8 ++++++++++++++++++++++ Wrong length of registry usership list for Text #13592: Imported on Dec 08, 2017, 23:51:23 Count: reported=212 found=211 Registry: text 10 unused member(s) in the Text registry Verifying Font registry Verifying Reference registry ++++++++++++++++++++++ ERROR #9 ++++++++++++++++++++++ Wrong reference count for Reference #166: Kubernetes: Up and Running: Dive into the Future of Infrastructure Count: reported=212 found=211 Registry: reference ++++++++++++++++++++++ ERROR #10 ++++++++++++++++++++++ Wrong length of registry usership list for Reference #166: Kubernetes: Up and Running: Dive into the Future of Infrastructure Count: reported=212 found=211 Registry: reference
Answer:
This is almost certainly a result of a bug that has been well documented but never found/fixed. The problem is with reference count (users of objects increment the count, or decrement it when no longer an object is used). In theory, if reference count drops to zero by mistake, you might lose an object (e.g. a picture), however, this has never been shown. Some rouge procedure must be doing wrong reference count updates. This error cannot be made into a warning because it needs to be subject to further research. If you suspect how the problem occurs, please write. It is possibly related to the complexity of using data source count, template count and then a "merged count" where the count differs between template, source and the merged object use.
If you happen to do error checks in short succession and see the error, you may have better hypothesis on how this occurs. Thank you.
See also: Wrong reference count for Text