|Anonymous | Login | Signup for a new account||21 Oct 19 06:43 BST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000311||Messenger Pro||misc||public||17 Apr 15 15:26||03 Dec 15 14:05|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Platform||intel core i7||OS||Windows||OS Version||8.1 64bit|
|Summary||0000311: Looping group-repair process|
|Description||MP V184.108.40.20681 Qt 5.4.1 Win 8.1 (64-bit)|
After my recent XP disk problems I'm slowly trying to get MP working on a W8.1 machine, using a full-app backup that was made (to Dropbox) on the 29th March. The XP machine it came from died about 6 days after that (intermediate backups are lost). It's possible that the files in the backup were damaged even on the 29th as I've no idea when the XP system's disk went bad, nor to what extent.
I just fetched uk.d-i-y (a busy newsgroup)'s traffic for the period from 29th March until now - about 5000 posts. That seemed to go ok. Then I opened the group in a viewer and started to delete threads whose subject suggests I'm not interested, especially those with 100+ posts per thread. After a while I returned to the all-groups viewer, selected the newsgroup, right-clicked it and chose Properties -> Tidy, planning to reorganise the folder hoping that'd make the continued pruning process more efficient.
It suggested about 20% of the in-use storage was dross. My normal habit would be to run a Repair, then a Compact. I can't quite remember the order of what happened, but after clicking Repair and maybe before clicking Compact, I got a pop-up message saying something like "can't determine bin size". Subsequently although I think I clicked Compact, and I think MP said it was starting & finishing something, MP has produced an 'initiating Repair' message box every 5 seconds or so. I shutdown MP after that.
|Tags||No tags attached.|
17 Apr 15 15:58
I've zipped-up 'group 72' from the 29th March backup, and the group 72 files from MP after I shut it down when the repair was looping, in case you want to look at them (I suppose to see if they were corrupt at the 29th March backup, or if something's gone wrong subsequently). The zip's around 7 MB in size, available at:
23 Apr 15 14:56
|I've encountered a similar issue. I've downloaded your archived group and have one of my own I can refer to as well.|
03 Dec 15 14:05
I'm also seeing this issue with the Mac version - 220.127.116.1183 Qt 5.4.1 Mac OS 10.9.5
Started a repair on a mailing list to receive repeated 'Repair initiated for group 'Hermes' '. Only way I managed to get back to sanity was to replace .gemini content from backup.
|17 Apr 15 15:26||JNicoll||New Issue|
|17 Apr 15 15:58||JNicoll||Note Added: 0000408|
|23 Apr 15 14:56||mark||Note Added: 0000409|
|23 Apr 15 14:56||mark||Assigned To||=> mark|
|23 Apr 15 14:56||mark||Status||new => confirmed|
|03 Dec 15 14:05||freder||Note Added: 0000410|
|Copyright © 2000 - 2019 MantisBT Team|