cocoaforge

Hi,

I like Vienna very much and use it on a daily basis during my software development cycle. I use Vienna to subscribe to some GitHub feeds, both for public and private repos, and also for rss feeds provided by Atlassian hosted Jira and Confluence instances. Vienna is for me the best way to get an overview of what happens between different software development teams in several locations.

What bothers me with Vienna is that it often becomes unresponsive on refreshing feeds. Even after it has shown a notification about "x new messages are available in y feeds", Vienna still is completely unresponsive for several seconds. The application is also shown as (Unresponsive) in the Apple task manager. As an end user I would except that I can continue to work normally with the application, and that any updates or refreshes on feeds are processed in the background and that the UI is updated as soon as the background processing has finished.

I use Version 3.0.0 Beta 20 :0fb193d: on Mac OS/X 10.9.2
My machine is a MacBookPro 2.7 Ghz Intel Core i7 with 16 GB memory and a 500GB SSD. Should be powerful enough to stay responsive.

I have experienced this unresponsiveness also with previous versions of Vienna and previous versions of OS/X.

Hi denisk -- yes, this is an issue we are aware of.

You're correct in identifying it as the main thread hosting both the network and filesystem access, whilst also running the UI (running the UI on the main thread is an Apple design requirement).

There's an Issue on our Github which broadly tracks the work do mitigate this. https://github.com/ViennaRSS/vienna-rss/issues/250. If you're interested in helping out, let us know.

Hi Echelon9,

Thanks for the response and good to know this is also identified as a concern to the commiters of the project.

I would love to help you out, however my working knowledge of Objective-C is zero, my main programming language is Java. I will definitely have a look at the code and see if I can understand what's happening, but don't expect major commits from my side.

That's fine. We'll keep people aware of updates via that Github issue tracker and the forums.