Repeatedly getting spinning beach ball while editing

Snit

I keep finding the app freezes for a minute or so when editing.

I did clear all caches and rebuild the databases, and have quit and restarted the app (as well as rebooting). Any other suggestions?

Andre

Is this happening after you clicked the reply/compose button, while editing or after you pressed the send button?

Snit

Andre After I click the reply button but before I hit send.

Snit

Hmmm, it did it again. Might be when it is sending the last. I will try to pay more attention. But this time it did it as I went to edit rules -- I was not editing a message.

Snit

Does seem to be when sending a message... but it lasts longer than the send. And it does not happen every time.

And has happened when downloading (I am only in text groups)

Edit: sorry... nope, just happens as I edit even without sending. Or downloading. Just happens a lot. I did clear caches again and rebuild, then quit and restart the app.

Andre

Strange.

What happens if you close USenapp and remove the cached files in:
/Users/[username]/Library/Caches/com.xoroxsoft.usenapp

And try not to keep too many hidden messages in the subscriptions (remove the old ones)
Also optimise the databases from time to time.

Maybe the above doesn't offer a solution, but I wouldn't know a solution otherwise. You could also choose to clear all subscriptions and see how it goes.

Snit

Andre

Away from home for a bit but will try and report back by the end of the week.

Snit

Snit Back home and using... and it is freezing up as I edit -- with nothing being sent.

Andre

Maybe there is a problem on your Mac with the spell checker.
Can you turn it off in Usenapp and see how it goes?

Snit

Andre Will do. Thanks.

Snit

Did... and it still gave me the beachball as I was editing. Darn.

Andre

I'm working on a completely new editor that can be tested in a week or two. Although I don't think your problem is with the current editor (or Usenapp in general) it could make a difference. I'll keep you informed.

Snit

Andre Thank you! Some time ago you said the editor was going to be replaced, and I have been waiting.

I will say I also have been using it a bit on an older MacBook Air and not having that issue there. So it very well could be tied to the system, though I am not seeing it in other apps (with the exception of once in BBEdit). My current work-around is to type longer replies in BBEdit and copy and paste over, which of course is not ideal.

What I will likely do is trash Usenapp and any related files (preferences and those in Application Support) and then re-install.

Andre

I hadn't thought of a corrupt database, but that explains the problem. I'll see if that can be caught.
Anyway, it's good to hear it's been resolved.

Snit Some time ago you said the editor was going to be replaced, and I have been waiting.

Yes, the new editor! I've been working on it for a while, but it's quite a bit of work. Fortunately, things are progressing well and testing can be done soon.

Snit

More info. Using Console I let it stream as I was in Usenapp. As it froze I see these messages:

database corruption at line 74317 of [02c344acea]

database disk image is malformed in "SELECT SUM(isread),COUNT(*) FROM msg_index;"

-[DBHeaders dbLoadMsgUnreadCount] database disk image is malformed

-[DBHeaders dbLoadMsgUnreadCount] Retry in 1 second. Attempt = 6

I do not pretend to fully understand that, but I am guessing that means the database is saved in a disk image and there is corruption there.

Snit

Went to the Usenapp folder in Application Support and deleted "db", "queue", "posts", and "articles" folders. Went back in and connected to my Usenet provider and selected the groups I like and all seems fine. Even grabbed the old rules.db and put that back in (did not want to recreate them all). Seems to be working fine now.

Seems somewhere along the way I corrupted a database.

Brawdy14

Great to hear that you've overcome the problem, Snit!

I'm going to have to 'get to grips' with using this facility!!

Help welcomed - always! 😅

Snit

Brawdy14

I am happy all is working again as well. ANY program can have its database go bad (well, any with a database, of course). Might be good if the app reported it to the user, but overall it is not like this is critical data. Very happy for @Andre's help here. And hopefully my report helps others.

Snit

Andre Your work is much appreciated. I ran into a snag, of course, but that happens. You have a happy customer and I look forward to the new editor.

Andre

I'll post the download link here to test the new version when it's available.

Snit

Andre Thank you. Happy to beta test it if you want. It is not like Usenet is mission critical for me.