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

LightBulb stuck? #29

Closed
mirh opened this issue May 9, 2017 · 52 comments
Closed

LightBulb stuck? #29

mirh opened this issue May 9, 2017 · 52 comments

Comments

@mirh
Copy link

mirh commented May 9, 2017

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)?

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 10, 2017

What version are you using?

@mirh
Copy link
Author

mirh commented May 10, 2017

1.6.3.3
And today it was stuck too.

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 10, 2017

I'll check it

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 12, 2017

Can you send your config file?

@mirh
Copy link
Author

mirh commented May 12, 2017

Configuration.dat
Besides, I found out that when I restart "graphics" (I wouldn't know if they stop and start gpu, dwm, or what) the problem gets fixed too.

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 16, 2017

Hey
Does it get unstuck if you press the "preview 24hr cycle" button?

@mirh
Copy link
Author

mirh commented May 16, 2017

Yes.

@mirh
Copy link
Author

mirh commented May 17, 2017

Ok, update.
I.. enabled/disabled (aka unstuck) the program earlier today (like around 7pm instead of 23 like - when I always notice/realize/remember of the problem).
And, fairly, it got set to like.. 5000K or something like that. And, just because, I had left the "24-h preview" button toggled enabled.
After 2 hours it still was set on that value though, and further pressing 24h preview had no effect this time.

@mirh
Copy link
Author

mirh commented May 19, 2017

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)

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 19, 2017

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.

@mirh
Copy link
Author

mirh commented May 20, 2017

Yes, no success.
I uploaded process fulldump here if it can help.

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 24, 2017

I tested it on two machines, trying sleep, hibernate, lock screen, leaving the PC for 2 days and it seems to work as expected.
Can you replicate your issue on any other PC?

@mirh
Copy link
Author

mirh commented May 24, 2017

I think my uptime is around 2 or 3 weeks (also including standby time in the count).
I also have another computer with similar cycles (aka no shutdowns) I could test, yes, but unfortunately it has Vista.
...
Whose "un-support" I'm not sure if being actually technical or just about you not caring about bug reports from there though?

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 24, 2017

I meant there was 2 days of standby, the PC itself ran for 5 days without LightBulb getting stuck.
I honestly don't remember whether LightBulb works on Vista or not. If you can install .NET framework 4.5.2 there then it probably should.

@mirh
Copy link
Author

mirh commented May 24, 2017

I think my uptime is around 2 or 3 weeks

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..
I guess like 3 weeks it's the time span?

If you can install .NET framework 4.5.2 there then it probably should.

It even supports 4.6 for all that it matters, and indeed it works!
I have set lb to really slightly dim to not disturb my dad, but I hope it still may do it.

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 24, 2017

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

@mirh
Copy link
Author

mirh commented May 24, 2017

Of course the funny thing is that to test the fix I'll have to restart the program 😛

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 24, 2017

See you in 2 weeks after that then ;)

@Tyrrrz
Copy link
Owner

Tyrrrz commented May 28, 2017

Try this, see if it gets stuck

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jun 12, 2017

2 weeks have passed, any news? 😛

@mirh
Copy link
Author

mirh commented Jun 12, 2017

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.

@mirh
Copy link
Author

mirh commented Jun 20, 2017

It happened agaaaaainnn
On the 7 1.6.3.3_T computer.

@mirh
Copy link
Author

mirh commented Jun 20, 2017

Ok correction.
Temperature does seems to increase and decrease normally and all.

Only 24-h preview seems fucked atm.

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jun 21, 2017

How is it fucked? Not changing the gamma or?

@mirh
Copy link
Author

mirh commented Jun 21, 2017

It doesn't do anything.
Ie, gamma doesn't change, and also the little "yellow bar" doesn't move.

Aside of that, the program still works effectively.

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jun 21, 2017

Did this also start happening only after a long time has passed?

@mirh
Copy link
Author

mirh commented Jun 21, 2017

Well, I guess so.
ProcExp says last time I started lightbulb was 30 May.

@Tyrrrz
Copy link
Owner

Tyrrrz commented Aug 29, 2017

Did you manage to replicate it on some other computer?

@mirh
Copy link
Author

mirh commented Sep 1, 2017

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.

@Tyrrrz Tyrrrz added the bug label Oct 2, 2017
@mirh
Copy link
Author

mirh commented Oct 10, 2017

Could this help?

@Tyrrrz
Copy link
Owner

Tyrrrz commented Oct 11, 2017

You can try

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jan 13, 2018

Still happens on 1.6.3.6?

@mirh
Copy link
Author

mirh commented Feb 18, 2018

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.
SEEMINGLY I hadn't have any more problem... So, I don't know solved?

@mirh mirh closed this as completed Feb 18, 2018
@mirh
Copy link
Author

mirh commented Mar 17, 2018

Surpriiise!

@mirh mirh reopened this Mar 17, 2018
@mirh
Copy link
Author

mirh commented Apr 13, 2018

So.. as another random datum, if I rotate the screen, gamma immediately sets to the right value.
"Stuck/unstuck" aren't probably the right terms then, since it actually seem to be always in the stuck position - but in the "instantaneous time window" of whatever special event (24-h cycle, on/off toggle, resolution change) I'm sending it.

@mirh
Copy link
Author

mirh commented May 4, 2018

Whatever timer the program use seems also to be fucked up or something.
I clicked on "disable for a minute".. And it like stayed off for 5 seconds.

On a second attempt timing was correct.

@mirh
Copy link
Author

mirh commented May 5, 2018

I stand correct. Lightbulb is batshit stuck period.
I cannot disable it at all now.

@mirh
Copy link
Author

mirh commented Jan 18, 2019

Still a thing

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jan 18, 2019

Can't do much about it :(

@mirh
Copy link
Author

mirh commented Jan 28, 2019

Would it help anything if I said every day at 18:00 the thing moves to ~4900K?
(and nothing else then, unless I manually toggle it)

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jan 28, 2019

What's the min/max temperature and what's the sunset time?

@mirh
Copy link
Author

mirh commented Jan 29, 2019

  "IsGammaPollingEnabled": false,
  "IsTemperatureSmoothingEnabled": false,
  "IsFullscreenBlocking": false,
  "IsCheckForUpdatesEnabled": true,
  "IsInternetSyncEnabled": true,
  "IsGeoInfoLocked": false,
  "TemperatureEpsilon": 50,
  "DefaultMonitorTemperature": 6600,
  "MinTemperature": 1300,
  "MaxTemperature": 6600,
  "MaximumTemperatureSmoothingDuration": "00:00:05",
  "TemperatureTransitionDuration": "01:30:00",
  "TemperatureUpdateInterval": "00:01:00",
  "GammaPollingInterval": "00:00:05",
  "CheckForUpdatesInterval": "06:00:00",
  "InternetSyncInterval": "06:00:00",
  "SunriseTime": "07:36:36",
  "SunsetTime": "17:13:22",

@Tyrrrz
Copy link
Owner

Tyrrrz commented Jan 29, 2019

So at 18:00 it goes from 1300 to 4900?

@mirh
Copy link
Author

mirh commented Jan 29, 2019

It goes from normal 6600K (which "unlocks" when I wake up my computer in the morning) to ~4900*.
Aside of this slight change, there's nothing else that seems to happen automatically.

*EDIT: today it was like 5033 instead

@mirh
Copy link
Author

mirh commented Aug 30, 2019

System.Reflection.TargetInvocationException was unhandled
  HResult=-2146232828
  Message=Exception has been thrown by the target of an invocation
  Source=mscorlib
  StackTrace:
       in System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       in System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       in System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       in GalaSoft.MvvmLight.Helpers.WeakAction.Execute()
       in GalaSoft.MvvmLight.CommandWpf.RelayCommand.Execute(Object parameter)
       in MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
       in System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
       in System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       in System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
       in System.Windows.Threading.DispatcherOperation.InvokeImpl()
       in System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
       in System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       in MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
       in System.Windows.Threading.DispatcherOperation.Invoke()
       in System.Windows.Threading.Dispatcher.ProcessQueue()
       in System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       in MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       in MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       in System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       in System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
       in System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
       in MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       in MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       in System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       in System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       in System.Windows.Application.RunDispatcher(Object ignore)
       in System.Windows.Application.RunInternal(Window window)
       in System.Windows.Application.Run(Window window)
       in LightBulb.App.Main()
  InnerException: 
       HResult=-2146233086
       Message=Specified argument was out of the range of valid values.
Nome parametro: blue
       ParamName=blue
       Source=LightBulb
       StackTrace:
            in LightBulb.Models.ColorIntensity..ctor(Double red, Double green, Double blue)
            in LightBulb.Models.ColorIntensity.FromTemperature(UInt16 temp)
            in LightBulb.Services.TemperatureService.UpdateGamma()
            in LightBulb.Services.TemperatureService.set_Temperature(UInt16 value)
            in LightBulb.Services.TemperatureService.UpdateTemperature(Boolean forceInstantSwitch)
            in LightBulb.Services.TemperatureService.set_IsRealtimeModeEnabled(Boolean value)
            in LightBulb.ViewModels.MainViewModel.set_IsEnabled(Boolean value)
            in LightBulb.ViewModels.MainViewModel.<.ctor>b__52_5()
       InnerException: 

Today, while as usual I had to enable/disable it, it crashed
LightBulbdump.zip

@Tyrrrz
Copy link
Owner

Tyrrrz commented Aug 30, 2019

Hey, can you try builds from here to see if it helps?

@mirh
Copy link
Author

mirh commented Aug 30, 2019

Sure.
But see you in another year or so with meaningful data 😄
EDIT: it seemingly it did reset my settings though? Could it be?

@mirh
Copy link
Author

mirh commented Sep 2, 2019

Well, isn't it funny. Now it uses to crash more or less on wake from standby.

Exception: System.Net.WebException
   in System.Net.HttpWebRequest.EndGetResponse(System.IAsyncResult)
   in System.Net.Http.HttpClientHandler.GetResponseCallback(System.IAsyncResult)

Exception: System.Net.Http.HttpRequestException
   in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   in LightBulb.Services.LocationService+<GetLocationAsync>d__2.MoveNext()
   in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   in LightBulb.ViewModels.RootViewModel+<>c__DisplayClass55_0+<<-ctor>b__4>d.MoveNext()
   in System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object)
   in System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   in System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   in System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   in System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   in System.Threading.ThreadPoolWorkQueue.Dispatch()
   in System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

@mirh
Copy link
Author

mirh commented Sep 21, 2019

With visual studio attached before suspending, in addition to the aforementioned

System.Net.Http.HttpRequestException
  HResult=0x80131500
  Messaggio=An error occurred while sending the request.
  Origin=mscorlib

Internal exception 1:
WebException: The remote name could not be resolved.: 'ip-api.com'

@Tyrrrz Tyrrrz mentioned this issue Oct 5, 2019
@Tyrrrz
Copy link
Owner

Tyrrrz commented Nov 8, 2019

Hey @mirh does it happen after rework?

@mirh
Copy link
Author

mirh commented Nov 9, 2019

The program has been running continuously just for 10 days now...
We'll see

@mirh mirh closed this as completed Nov 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants