|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6 |
|
| Author |
|
JonGl
Regular Joined: Oct 14, 2009 Post Count: 55 Status: Offline |
Howdie- I got upgraded to the latest MacSword in recent days, (2.2.11-1740), and now, when it's open, it runs at well over 100% of CPU usage. It brings my 2.66mhz, w/ 4 gigs of ram to its knees, with the fan running full-blast after a short while. Am I unique with this problem? Or did something go wrong with the update? TIA -Jon |
||
|
|
mdbergmann
Inventory Germany Joined: Jun 12, 2008 Post Count: 637 Status: Offline |
Hi. This release brings back the background indexer which indexes all your modules. It was removed some time ago because people complained about the CPU usage but there was a feature request here and I actually like it as well. However you can disable it. Type this in a command line:
Manfred |
||
|
|
JonGl
Regular Joined: Oct 14, 2009 Post Count: 55 Status: Offline |
Thanks for the guidance! That seems to have fixed it. Thanks. Oh, and I took the lazy way out, and used Property List Editor to make the change--mostly because I was curious if it was already flipped to on or not, before I reinstalled the app. -Jon |
||
|
|
mdbergmann
Inventory Germany Joined: Jun 12, 2008 Post Count: 637 Status: Offline |
Yeah, you can of course also use the Property List Editor tool. Per default this setting should be disabled. But if you came from MacSword 2.0.x then it's possible this setting was still enabled in preferences. Manfred |
||
|
|
JonGl
Regular Joined: Oct 14, 2009 Post Count: 55 Status: Offline |
Yeah, you can of course also use the Property List Editor tool. Per default this setting should be disabled. But if you came from MacSword 2.0.x then it's possible this setting was still enabled in preferences. Manfred Yeah, I had 2.0 installed from way back. Maybe that was why I was never able to use the app. I didn't realize it at the time. Was this feature also part of the constant crashing problem, then? -Jon |
||
|
|
mdbergmann
Inventory Germany Joined: Jun 12, 2008 Post Count: 637 Status: Offline |
Yeah, I had 2.0 installed from way back. Maybe that was why I was never able to use the app. I didn't realize it at the time. Was this feature also part of the constant crashing problem, then? There were module database problems which were causing crashes. The indexing code wasn't that stable as well. So yes, maybe that was the cause for some crashes. Manfred |
||
|
|
|
Current timezone is GMT May 25, 2013 7:17:43 PM |
