Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Countdown hangs on OS X 10.7 Lion #15

Closed
kristofferR opened this issue Jul 21, 2011 · 41 comments
Closed

Countdown hangs on OS X 10.7 Lion #15

kristofferR opened this issue Jul 21, 2011 · 41 comments

Comments

@kristofferR
Copy link

The blocking itself is working fine, but the countdown always stops a few seconds after it was initiated. By quitting and starting the application again the counter starts working.

@dbalatero
Copy link

+1 on this.

@SteveBell
Copy link

Looking for Lion support as well.

@tbatchelli
Copy link

+1 on this too

@jtoy
Copy link

jtoy commented Aug 14, 2011

I cant even get the countdown to start

@khanhlnq
Copy link

+1

@slambert
Copy link

Running it on Lion right now. Seems to work fine. If anyone can give more details on this we can reopen it...

@maattdd
Copy link

maattdd commented Dec 12, 2011

I'm on 10.7.2, and I confirm that sometimes (but I haven't been able to precisely say when for the moment), the countdown printing is blocked, but the actual timer works.

What kind of details do you need ?

@kristofferR
Copy link
Author

How long did you keep it running, slambert? It seems to work fine the first minute or so, but then the timer hangs both in the app and in the dock.

@slambert
Copy link

15 minutes, no problems. 10.7.2

sometimes... can we narrow that down a bit?

@kristofferR
Copy link
Author

10.7.0-10.7.2 every time after a minute or two - Mid 2009 17" Macbook Pro. It worked fine on Snow Leopard.

@slambert
Copy link

Thanks kristofferR. Not sure how we'll solve it yet, but if anyone has more info...

@slambert slambert reopened this Dec 13, 2011
@jkmaxwell
Copy link

+1, but it's low priority/low impact. the countdown initiates and progresses in the background, but the display doesn't update. quitting and restarting the app fixes the problem without any impact on the countdown itself.

@franciscolourenco
Copy link

I have this problem to.. I've set the countdown to 1min and it always stops with 53s left..

@slambert
Copy link

I've finally seen this happen myself. Work-around: restart SelfControl and it's fine. Long term solution – not sure...

@psugihara
Copy link

+1, Lion support would be great!

@SteveBell
Copy link

How can you tame this bug? Can't anybody provide any log? Not breaking anything but having to close+open the app whenever a user needs a countdown is pretty annoying.

@Sumukh
Copy link

Sumukh commented Jan 30, 2012

edit: There are some weird issues with ghost files not showing up in Xcode. MainWindow.xib and InfoStrings. Might be a local thing or a Xcode bug.

I just did a quick test of a 15 minute block and I can't replicate it when I build from source. Will confirm later with longer tests.

I've put a compiled version here (let me know if you'd prefer a fork) I didn't actually change all that much but see if this works for you: http://sumukh.me/7HlQ

@SteveBell
Copy link

hey Sumukh, thx for the effort. I tried your version and entered 2h and something minutes and got a hang on 02:08:25. As before restarting Selfcontrol brings the countdown back to it's correct time and it's running again. Very strange.

@slambert
Copy link

slambert commented Feb 1, 2012

@Sumukh thanks for giving it a shot! When you have it worked out we'll be happy to roll in your changes. I think we're sitting on a german translation release that can go out at the same time.

@Sumukh
Copy link

Sumukh commented Feb 1, 2012

@SteveBell Well that's disappointing. I'd love do some rapid debugging with the thing out but I can't stop and reset the app, ending up waiting the timer to legitimately finish (changing the time doesn't seem to properly exit the app).

@slambert
Copy link

slambert commented Feb 1, 2012

@Sumukh You could change the interval length to 1m for the purposes of testing: https://github.com/slambert/selfcontrol/wiki/Tweaking-Max-Block-Length-and-Block-Length-Interval

@Sumukh
Copy link

Sumukh commented Feb 1, 2012

@slambert Oh wow. Awesome, thanks!
@SteveBell Could you keep running the app I uploaded in normal use and the next time it crashes note the exact time on your computer (8:19:30 PM etc)
Then go to the Console (do a search for Console) and then search for self (which will give access to the log statements when it stops displaying). I'm currently polluting the Console log with tons of Logging statements to figure out what happens when it crashes. If you could then upload the logs around the time it crashed, that'd be awesome. :)

I haven't personally seen a freeze yet, but I'll set aside some time to test it out more.

@Sumukh
Copy link

Sumukh commented Feb 1, 2012

I think this could solve it. It seemed to be a couple of brackets that weren't inserted. Please test it out (and be sure to launch this version of it :] ) and let me know if it works for you http://sumukh.me/Npzt

I tested on Lion with a couple of one minute ones and a 2hr one that is still going on.

@SteveBell
Copy link

hey Sumukh, thanks sooo much for taking care of this. Tried your latest version with several short countdowns and one longer 3h sth. No problems so far. Will do more testing soon and report back if this should show up again. Can't wait for your fixed to be pulled. Also great stuff cleaning up the log file in #17. Cheerios :)

@jkmaxwell
Copy link

Works here on OS X 10.7.2, set for 10 hours, blacklist mode. Running for
10 minutes now without stopping. Thanks!

On Thu, Feb 2, 2012 at 12:41 AM, Steve Bell <
reply@reply.github.com

wrote:

hey Sumukh, thanks sooo much for taking care of this. Tried your latest
version with several short countdowns and one longer 3h sth. No problems so
far. Will do more testing soon and report back if this should show up
again. Can't wait for your fixed to be pulled. Also great stuff cleaning up
the log file in #17. Cheerios :)


Reply to this email directly or view it on GitHub:
#15 (comment)

@Sumukh
Copy link

Sumukh commented Feb 4, 2012

Just wanted to mention that I've put up a pull request ( #36 ), so if you notice anything you can comment there.

Thanks for helping me test it :)

@SteveBell
Copy link

Argh. Bad news. Just entered a 30 min countdown and experienced a hang on 29:49. I get minutely msg in console saying:
before
08.02.12 01:37:36,477 [0x0-0x35b35b].org.eyebeam.SelfControl: 2012-02-08 01:37:36.474 org.eyebeam.SelfControl[26952:1607] INFO: Block successfully added.
08.02.12 01:38:36,703 org.eyebeam.SelfControl: 0
...
08.02.12 01:48:36,314 org.eyebeam.SelfControl: 0
08.02.12 01:49:36,920 org.eyebeam.SelfControl: 0
etc

As already known: a restart of Selfcontrol brings the account back to the correct time.

@Sumukh
Copy link

Sumukh commented Feb 10, 2012

I haven't personally experienced any more hangs, but I'll look into other situations. A work around would be get rid of the badge (I have yet to test it, but its a hypothesis). Do you really need the badge?

@slambert
Copy link

I actually experienced this with the new version as well. Don't have my console log though. What are you calling "the badge?"

@Sumukh
Copy link

Sumukh commented Feb 26, 2012

CStigler made some comments/suggestions about the fix and I just took a quick stab with his suggestions.
It seems to work so far.

Could you try it out and let me know if it works well for you?
Known issues: Has no badge on Lion.
Binary here: http://sumukh.me/bxa0
Binary with badges working: http://sumukh.me/10wq

@jkmaxwell
Copy link

worked well on a macbook pro running 10.7.2

On Sun, Feb 26, 2012 at 3:42 PM, Sumukh Sridhara <
reply@reply.github.com

wrote:

CStigler made some comments/suggestions about the fix and I just took a
quick stab with his suggestions.
It seems to work so far.

Could you try it out and let me know if it works well for you?
Binary here: http://sumukh.me/bxa0


Reply to this email directly or view it on GitHub:
#15 (comment)

@Jhering
Copy link

Jhering commented Feb 27, 2012

Binary with badges working: http://sumukh.me/10wq


it works well on my Lion 10.7.3

Why not upgrade the official binary package in git's WIKI ,which is still ugly on Lion?

@Jhering
Copy link

Jhering commented Feb 27, 2012

The official 1.3 is ugly on my Lion.It doesn't work well.
In blacklist mode, when it begins, besides the website in blacklist the other hosts can not visit correctly neither. And though the countdown is over, the website in blacklist still can not visit.....OMG...
But the version here:
Binary with badges working: http://sumukh.me/10wq

resolve all the bug in LION. It's works well utill now------I only test it for several hours.
Keep going, Selfcontrol!
Your programm help my life, i love it.

@jkmaxwell
Copy link

This one still has the "hanging countdown on launch" issue

On Mon, Feb 27, 2012 at 3:25 AM, Jhering <
reply@reply.github.com

wrote:

The official 1.3 is ugly on my Lion.It doesn't work well.
In blacklist mode, when it begins, besides the website in blacklist the
other hosts can not visit correctly neither. And though the countdown is
over, the website in blacklist still can not visit.....OMG...
But the version here:
Binary with badges working: http://sumukh.me/10wq

resolve all the bug in LION. It's works well utill now------I only test it
for several hours.
Keep going, Selfcontrol!
Your programm help my life, i love it.


Reply to this email directly or view it on GitHub:
#15 (comment)

@Sumukh
Copy link

Sumukh commented Feb 28, 2012

@jkmaxwell :( So as soon as you typed in your password, it froze up? Just to humor me, can you confirm that you were using the beta version (with or without the badges? - The app name should have some form of beta in it)? Also, if you tell me what time you set it for, I can start testing with that instead.

This might be too much to ask but can you try the two versions above? I doubt there'd be that big of a difference, but this is becoming really tricky. It seems to work in most use cases, but it isn't resolved until it doesn't occur.

@SteveBell
Copy link

Honestly loosing overview over the versions to test. Could you sum up in one post, what versions you want us to test with links?

@Sumukh
Copy link

Sumukh commented Mar 4, 2012

Yes. I'll make a pull request with the changes required and a binary in there today.

@utechtl
Copy link

utechtl commented May 12, 2012

i'm not sure if the issued been ignored or anything but, could it be when you switch to desktop 2 (or a different one) that causes it to happen? Thats when it does that to me.

@Sumukh
Copy link

Sumukh commented May 13, 2012

It happens randomly for me, but I don't know if we really have a 100% fix for this. See: #36

@cstigler
Copy link
Member

Should be fixed now, update to 1.4 and reopen if anything is still broken.

@nbroyles
Copy link

Just a heads up, I just saw this happen on Mountain Lion (10.8.2) with version 1.4 of the app. Does not happen consistently though and is fixed by restarting the app, as others have mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests