-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
LightBulb stuck? #29
Comments
What version are you using? |
1.6.3.3 |
I'll check it |
Can you send your config file? |
Configuration.dat |
Hey |
Yes. |
Ok, update. |
Another hint: I enabled the 24-h preview this evening, and I noticed the slim orange bar progressed like 10-20 pixels, then stopped (way far from the end of the "bar" which I guess would mean night, and irregardless of how many times I then tried to toggle the button) |
This is so confusing. Have you tried if it works with default settings? I noticed you have your min. temperature manually set below the threshold. |
Yes, no success. |
I tested it on two machines, trying sleep, hibernate, lock screen, leaving the PC for 2 days and it seems to work as expected. |
I think my uptime is around 2 or 3 weeks (also including standby time in the count). |
I meant there was 2 days of standby, the PC itself ran for 5 days without LightBulb getting stuck. |
Ok, correction, I just came home and task manager is like ticking for 17:09:47:59. So it's like 2 weeks and half, not counting for standby. So, an educate guess of like middle April being last time I started it, and firsts of May when I reported it..
It even supports 4.6 for all that it matters, and indeed it works! |
So I was eating and I think I have an idea of what could be the problem. Will try this week if it works. Note to self: device context might be becoming stale |
Of course the funny thing is that to test the fix I'll have to restart the program 😛 |
See you in 2 weeks after that then ;) |
Try this, see if it gets stuck |
2 weeks have passed, any news? 😛 |
Well, on the one hand I had no problems.. On the other, it's even true that -contrarily than in april/may- I not-so-rarely "interacted" with the program. |
It happened agaaaaainnn |
Ok correction. Only 24-h preview seems fucked atm. |
How is it fucked? Not changing the gamma or? |
It doesn't do anything. Aside of that, the program still works effectively. |
Did this also start happening only after a long time has passed? |
Well, I guess so. |
Did you manage to replicate it on some other computer? |
I'm quite joyful to report I could get lightbulb to bug in, more or less, a day and half. So.. well whatever you'll want to test it shouldn't take too long to confirm. |
Could this help? |
You can try |
Still happens on 1.6.3.6? |
Ok so.. I just closed lightbulb (for reasons) and realized I shouldn't have had since I was on a 3-4 weeks spree of keeping it running. |
Surpriiise! |
So.. as another random datum, if I rotate the screen, gamma immediately sets to the right value. |
Whatever timer the program use seems also to be fucked up or something. On a second attempt timing was correct. |
I stand correct. Lightbulb is batshit stuck period. |
Still a thing |
Can't do much about it :( |
Would it help anything if I said every day at 18:00 the thing moves to ~4900K? |
What's the min/max temperature and what's the sunset time? |
|
So at 18:00 it goes from 1300 to 4900? |
It goes from normal 6600K (which "unlocks" when I wake up my computer in the morning) to ~4900*. *EDIT: today it was like 5033 instead |
Today, while as usual I had to enable/disable it, it crashed |
Hey, can you try builds from here to see if it helps? |
Sure. |
Well, isn't it funny. Now it uses to crash more or less on wake from standby.
|
With visual studio attached before suspending, in addition to the aforementioned
|
Hey @mirh does it happen after rework? |
The program has been running continuously just for 10 days now... |
Like.. This morning I resumed from standby, it was stuck to night temp.
Tonight then, I just realized it didn't already triggered.
Only manually disabling/enabling unstucked the thing, but I wouldn't know if tomorrow it mightn't happen again.
Is there anyway I can take a memory dump or something to add more detail (I still haven't restarted the program)?
The text was updated successfully, but these errors were encountered: