> On 11 Sep 2018, at 11:28, Christiaan Hofman <cmhof...@gmail.com> wrote: > > > >> On 11 Sep 2018, at 09:01, Masso Chailly <emess...@gmail.com >> <mailto:emess...@gmail.com>> wrote: >> >> Oh, I’ve got the same ‘problem’, but when I save the library (not every time >> but at random instants). >> So far I thought it was just because the library is big (>7000 entries). I >> would be happy if it could be improved. >> >> Masso >> >> >> >>> On 11 Sep 2018, at 1:26 PM, Jan David Hauck <jan.d.ha...@ucla.edu >>> <mailto:jan.d.ha...@ucla.edu>> wrote: >>> >>> BibDesk has recently developed a habit of becoming unresponsive and giving >>> me the beach ball when I collapse a group field with many entries, in >>> particular Authors and Keywords (by collapsing I mean clicking "Hide" >>> above the field). True, my library has about 3800 entries, so authors and >>> keywords are likely a lot more than that. But I don't remember it taking >>> that long, sometimes over a minute. >>> It only happens upon hiding the group fields, not when showing them. >>> >>> Any ideas? >>> >>> >>> Console has these entries: >>> >>> default 21:12:05.806789 -0700 kernel process BibDesk[9417] thread >>> 2081476 caught burning CPU! It used more than 50% CPU over 180 seconds >>> (actual recent usage: 71% over ~126 seconds). Thread lifetime cpu usage >>> 118.938301s, (115.287758 user, 3.650543 sys) ledger balance: 90001488498 >>> mabs credit: 118850457806 mabs debit: 28848969308 mabs limit: 90000000000 >>> mabs period: 180000000000 ns last refill: 126404685964 ns. >>> >>> default 21:12:05.853275 -0700 symptomsd Received CPU usage >>> trigger: >>> BibDesk[9417] () used 90.00s of CPU over 126.40 seconds (averaging 71%), >>> violating a CPU usage limit of 90.00s over 180 seconds. > > > Strange, I don’t think we changed anything related to this action in quite a > while. Perhaps something changed in the OS that after this. And we really are > not doing much when you collapse an outline item (a lot more happens when you > expand it). > > Could you take a sample of BibDesk when this happens? You can take a sample > using Activity Monitor, select the BibDesk process and choose View > Sample > Process. You could add it to a bug report. > > Christiaan
No need to get a sample and file a bug report. I was able to reproduce it myself, and found the cause and a solution. No idea why it would be only occurring now, as it has always worked the same, so probably Apple made a system a lot more vulnerable to this problem. Anyway, the next release (and next nightly) should solve this problem. Christiaan
_______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
