Hi All
Congratulations on the release of V2, I'm all up and running and it's working well,
One question is there any setting that automatically causes the program to close or did I have a crash??
I am running an FT8 bot and I noticed on my online log that I hadn't made any QSO's in a while, when I went to the PC I noticed that Log4om had closed,
I doubt there is a setting to shut it after a period of time or is there,
If not I had a crash, everything else is stable on the PC
Thanks
Trevor
EI2GLB
Crash or auto close
- G4POP
- Log4OM Alpha Team
- Posts: 10813
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Crash or auto close
Sounds like the bot closed it
That's the trouble with unattended operating you don't see the actions leading up to the incident
That's the trouble with unattended operating you don't see the actions leading up to the incident
73 Terry G4POP
Re: Crash or auto close
Not sure the Bot is to blame but I'll keep an eye on it,
Lots of tweaking to get everything running together so an odd clitch is going to pop up,
Thanks
Trevor
EI2GLB
Lots of tweaking to get everything running together so an odd clitch is going to pop up,
Thanks
Trevor
EI2GLB
Re: Crash or auto close
Hi.
About same issue here..
Upgraded from the 2 first versions of log4omV2, to latest .20 this morning.
Issue with the first versions was 100% cpu after running program for some minutes, but this seams to be fixed now.
Issue now is that programs suddenly closes after running for a few hours without any error messages...
Computer here is HP 600 series workstation, dual xenon, 32gb ram and windows 10 x64.
Btw. Log4om r1 is stable.
Regards Bjørn/ la5vsa
About same issue here..
Upgraded from the 2 first versions of log4omV2, to latest .20 this morning.
Issue with the first versions was 100% cpu after running program for some minutes, but this seams to be fixed now.
Issue now is that programs suddenly closes after running for a few hours without any error messages...
Computer here is HP 600 series workstation, dual xenon, 32gb ram and windows 10 x64.
Btw. Log4om r1 is stable.
Regards Bjørn/ la5vsa
Re: Crash or auto close
Still closing in middle of qso... Here is from eventlog Windows
.NET Runtime
Application: L4ONG.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Threading.Thread.GetCurrentThreadNative()
at System.Threading.Thread.get_CurrentThread()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireQueuedTimerCompletion(System.Object)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Application Error
Programnavn med feil: L4ONG.exe, versjon: 2.2.0.0, tidsangivelse: 0x5e2d9531
Modulnavn med feil: KERNELBASE.dll, versjon: 10.0.18362.628, tidsangivelse: 0x54734dee
Unntakskode: 0xe0434352
Feilforskyvning: 0x00113db2
Feil prosess-ID: 0x51cc
Feil starttid for program: 0x01d5d7411c9feb2a
Feil programbane: C:\Program Files (x86)\IW3HMH\Log4OM NextGen\L4ONG.exe
Feil modulbane: C:\Windows\System32\KERNELBASE.dll
Rapport-ID: 7a86469a-2c43-491e-8d70-bcf9b825bbd8
Fullstendig navn på feilpakke:
Relativ program-ID for feilpakke:
Going back to version 1 until fixed.
regards
la5vsa Bjorn
.NET Runtime
Application: L4ONG.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Threading.Thread.GetCurrentThreadNative()
at System.Threading.Thread.get_CurrentThread()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireQueuedTimerCompletion(System.Object)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Application Error
Programnavn med feil: L4ONG.exe, versjon: 2.2.0.0, tidsangivelse: 0x5e2d9531
Modulnavn med feil: KERNELBASE.dll, versjon: 10.0.18362.628, tidsangivelse: 0x54734dee
Unntakskode: 0xe0434352
Feilforskyvning: 0x00113db2
Feil prosess-ID: 0x51cc
Feil starttid for program: 0x01d5d7411c9feb2a
Feil programbane: C:\Program Files (x86)\IW3HMH\Log4OM NextGen\L4ONG.exe
Feil modulbane: C:\Windows\System32\KERNELBASE.dll
Rapport-ID: 7a86469a-2c43-491e-8d70-bcf9b825bbd8
Fullstendig navn på feilpakke:
Relativ program-ID for feilpakke:
Going back to version 1 until fixed.
regards
la5vsa Bjorn