1 of 5 |
1 |
Ever since I switched from Eventbox to Socialite my apps lock up after having Socialite running for 1-2 hours. Just to be sure I tried running stuff without Socialite running and had no issues. Basically I get the pinwheel of death, try to do force quit and all my apps say not responding. Anyone else having this issue? I’m also not sure if the issue is caused by another app while running Socialite.
Basically I get the pinwheel of death, try to do force quit and all my apps say not responding. Anyone else having this issue? I’m also not sure if the issue is caused by another app while running Socialite.
I am having the same issue. Beachball every few hours requiring a hard reset on system 10.5.8. Force quit does not work. Gave up after the first day since facebook doesn’t work either and I had to destroy all my settings/smartfolders, etc. to get unread items to stay unread. Honestly, really not sure how so much stuff got so broken so quickly. Will give it a try when the next beta shows up in hopes that I didn’t waste my money purchasing this app. I get this is beta software, but I figure being useable without bringing my entire--normally rock solid--system down every few hours is a pretty low bar.
I replied in another thread too, since I was seeing the same behavior with beta 3 on Mac OS 10.5.8. I read a user still has the problem with beta 4. Do the developers post responses here?
Hi Guys
We’re around Monday - Friday (9-5 UK time), and do post responses here. If you’re able to reproduce this reliably, could you let us know the details below:
1. Your OS version
2. What other applications are you running at the same time as Socialite? [Please include any menu items or Preference Panes]
We run Socialite all-day every day and haven’t been able to reproduce the issue, so any further details would be appreciated.
Thanks!
Nik
Hi Guys
We’re around Monday - Friday (9-5 UK time), and do post responses here. If you’re able to reproduce this reliably, could you let us know the details below:
1. Your OS version
2. What other applications are you running at the same time as Socialite? [Please include any menu items or Preference Panes]
We run Socialite all-day every day and haven’t been able to reproduce the issue, so any further details would be appreciated.
Thanks!
Nik
1. OS X 10.5.8
2. Safari, Mail, iChat, iTunes, Waveboard, iCal, Daylite
Wondering if multiple Growl notifications is causing any problem, it’s the only thing low level enough I can think of to cause multiple apps to lock, but you know more than me.
I am hesitant to try to reproduce as I have a fresh OS install on my box and don’t want to want to corrupt anything with hard reboots. I will see if I can install on another Mac and reproduce, may be a while.
Thanks
Josh
Hi Guys
We’re around Monday - Friday (9-5 UK time), and do post responses here. If you’re able to reproduce this reliably, could you let us know the details below:
1. Your OS version
2. What other applications are you running at the same time as Socialite? [Please include any menu items or Preference Panes]
We run Socialite all-day every day and haven’t been able to reproduce the issue, so any further details would be appreciated.
Thanks!
Nik
To expand on my initial post and respond to your twitter reply:
1. OS is 10.5.8. (Machine is a MacBookPro, 2 GHz Intel Core Duo, so vintage late ‘06-early ‘07 or so.)
2. Other apps that were running during most recent crash, (with beta 4.) Version numbers in parentheses:
--Safari (4.0.3, Glims 1.0b23)
--iTunes (9.0.1) I’ve never had iTunes running during any other crash.
--XChat Aqua (0.16.0)
--Fresh (1.2.1)
--Quicksilver (B54 [3815])
--Reader Notifier (1.10)
--Meteorologist (1.4.
--ShoveBox (1.7.4)
--Alarm Clock 2 (2.4.5)
Pref panes:
--Growl (1.2)
--MenuMeters (1.3)
Other crashes happened with Beta 2. I missed beta 3. In general, everything listed above except iTunes has been running during other crashes.
Regarding reproducible steps, the only step required for this problem to happen is for me to start up Socialite. It happens EVERY TIME I use the app, generally within 4-6 hours of starting the app under beta 2, often when I was not even home. It happened approximately 3 hours into use of beta 4.
First symptom is generally that tweets stop coming in--no growl notifications and no increasing message count in the menubar. I follow about 400 users across several time zones, including a couple of news services, so it is unusual to go any real length of time without receiving any new tweets. When bringing the app to the front, the dreaded beach ball appears.
The app cannot be Force Quit, and neither Terminal nor Activity Monitor can be opened to attempt to quit any associated processes or even see what specific processes are stuck. The beachball then spreads to other apps, and a hard restart is the only way out. I looked at the console logs after the last crash to see if anything unusual popped out at me, but really, nothing did.
I *really* want this client to work, as other twitter clients available for OSX simply do not meet my needs and many of them seem to be Adobe Air based, which is not really a plus from my perspective.
While I am happy to help out, I am hesitant to run this app.
I’ll add my 0.02 to this thread.
I had lockup problems with Beta 3 and now Beta 4. After going through a period of trial and error, trying to figure what was causing the lockups, I seem to be zoning in on Socialite. I had been having lockups a few times per day, but now that I have not used Socialite for 2 days, I have not had a lock up since.
The behavior seems to start with Mail becoming non-responsive with a spinning beach ball. Then one-by-one, after a few minutes, other apps go the same route, including Socialite. They will not be killed, either using Force Quit or by using ‘kill’ from the CLI. The only recourse is to shut my MBP down and re-boot.
The apps that I typically have running are:
1. Mail
2. iChat
3. iCal
4. Address Book
5. iTunes
6. Skype
7. Things
8. Safari
9. Growl
10. PGP Whole Disk Encryption
11. Expose
12. Spaces
13. Time Machine
14. Missing Sync for Win Mobile (Moving to iPhone soon… 
15. Preview
16. RapidWeaver
17. iWork ‘09
18. OpenOffice
I also have a few dashboard widgets running.
Not all apps are running all the time, but numbers 1 through 14 are either loaded at boot/login or are frequently used each day.
I have not looked at RAM usage to see if there is perhaps a memory leak, but it is bad enough that I cannot use Socialite at present without losing other apps and possibly associated documents/data.
As with others, it does not happen right away, but after a period of time, typically within 2-3 hours.
I am on a Spring 2009 Unibody 17 inch MacBook Pro, OSX 10.5.8 (fully updated), 2.93 Ghz Core 2 Duo, 4 Gb RAM, 7200 rpm HD, running with the nVidia 9600M enabled.
I’d really like to see this resolved with Socialite as EB has been a great application and FWIW, as you can see, I also use RapidWeaver…
Thanks
<snip>
2. Other apps that were running during most recent crash, (with beta 4.) Version numbers in parentheses:
--Safari (4.0.3, Glims 1.0b23)
--iTunes (9.0.1) I’ve never had iTunes running during any other crash.
--XChat Aqua (0.16.0)
--Fresh (1.2.1)
--Quicksilver (B54 [3815])
--Reader Notifier (1.10)
--Meteorologist (1.4.
--ShoveBox (1.7.4)
--Alarm Clock 2 (2.4.5)
Pref panes:
--Growl (1.2)
--MenuMeters (1.3)
First symptom is generally that tweets stop coming in--no growl notifications and no increasing message count in the menubar. I follow about 400 users across several time zones, including a couple of news services, so it is unusual to go any real length of time without receiving any new tweets. When bringing the app to the front, the dreaded beach ball appears.
<snip>
I *really* want this client to work, as other twitter clients available for OSX simply do not meet my needs and many of them seem to be Adobe Air based, which is not really a plus from my perspective.
While I am happy to help out, I am hesitant to run this app.
Just wanted to add that I decided to give it a go without Growl running. (That is, completely not running, not just disabled for Socialite.) Socialite has been up and running for approximately 9 hours now without bringing down my system. Will see how it does overnight.
same problem. socialote freeze my system many times for a couple seconds:
1. mail
2. indesign
3. photoshop
4. illustrator
5. ical
6. things
7. adium
8. skype
9. dropbox
10. google search box
11. textexpander
12. little snitch
13. busysync
14. growl
now, disable growl to test today.
Just wanted to add that I decided to give it a go without Growl running. (That is, completely not running, not just disabled for Socialite.) Socialite has been up and running for approximately 9 hours now without bringing down my system. Will see how it does overnight.
I turned growl proper on before bed. Growl notifications for Socialite were disabled at the app level and at the pref pane level.
Socialite beachballed within two hours, and brought my machine down with it.
I have disabled Growl as per the recent posts. A couple of hours so far without beachballs...we’ll see how it goes for a while.
I have 1.0 now and just waiting for clarification on registration (EventBox serial number not working as per my new thread/post).
Thanks
Just wanted to add that I decided to give it a go without Growl running. (That is, completely not running, not just disabled for Socialite.) Socialite has been up and running for approximately 9 hours now without bringing down my system. Will see how it does overnight.I turned growl proper on before bed. Growl notifications for Socialite were disabled at the app level and at the pref pane level.
Socialite beachballed within two hours, and brought my machine down with it.
So, does it appear that Socialite works with Growl disabled?
Just wanted to add that I decided to give it a go without Growl running. (That is, completely not running, not just disabled for Socialite.) Socialite has been up and running for approximately 9 hours now without bringing down my system. Will see how it does overnight.I turned growl proper on before bed. Growl notifications for Socialite were disabled at the app level and at the pref pane level.
Socialite beachballed within two hours, and brought my machine down with it.
So, does it appear that Socialite works with Growl disabled?
I am now going on 5+ hours without a beachball...Growl disabled....so far so good…
This is with 1.0 release BTW, as of today....
HTH
I’ve had similar problems. This on OS X 10.6.2 and the latest Growl 1.2. There seems to be a threshold, or perhaps it’s just that when there are a lot of notifications pending it increases the chances of some type of deadlock or other related event occurring. Disabling Growl notifications in Socialite “fixes” the issue. In my case it is possible to force quit Socialite when the issue occurs.
Just had it yesterday. Guess it happens, after Socialite is running for quite some time on your system. Can’t see it happening, if you launch it, read new events and quit.
Btw, got my twitter account broken after a force reboot. Tries to authenticate, showing a built-in browser, but nothing happens.
Just a quick note.
I am now about 3 days into my use of 1.0. It locked up my apps this morning, even with Growl disabled (globally).
So something else beside Growl is going on, albeit Growl may be exacerbating some underlying problem so that it occurs more frequently.
HTH
1 of 5 |
1 |
