INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Multiple crashes during auto import from network  (Read 2193 times)

Opawesome

  • Recent member
  • *
  • Posts: 32
Multiple crashes during auto import from network
« on: July 04, 2020, 11:37:00 am »
Hi,

I am experiencing crashes. They occur about 1-2 minutes after I launch auto import of files located a network share.

This happens on a fresh install on my new HTPC.

Previous auto-imports performed on my former HTPC had no issues.

Attached are the logs.

Any help would be greatly appreciated.

Many thanks.

OP
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #1 on: July 04, 2020, 01:04:40 pm »
Could be a bad file.  Could you try MC26?

This doesn't look good:

0114047: 2008: General: CFileSystemManager::AnalyzeDrive: Error using connection '\\MOZART\': 53
0114047: 2008: General: CFileSystemManager::AnalyzeDrive: Drive does not exist (drive: \\MOZART\, filename: \\MOZART\\MOZARTHolst - Cotswolds Symphony, Walt Whitman Overture, A Hampshire Suite March, The Perfect Fool Ballet Music, Scherzo for Orchestra (Douglas Bostock)\, type: 0, attributes: 0)

and I see you're importing CUE files.  Try turning that off in the Import settings.
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #2 on: July 04, 2020, 02:24:15 pm »
Quote from: JimH on July 04, 2020, 01:04:40 pm
Could be a bad file.  Could you try MC26?

This doesn't look good:

0114047: 2008: General: CFileSystemManager::AnalyzeDrive: Error using connection '\\MOZART\': 53
0114047: 2008: General: CFileSystemManager::AnalyzeDrive: Drive does not exist (drive: \\MOZART\, filename: \\MOZART\\MOZARTHolst - Cotswolds Symphony, Walt Whitman Overture, A Hampshire Suite March, The Perfect Fool Ballet Music, Scherzo for Orchestra (Douglas Bostock)\, type: 0, attributes: 0)

and I see you're importing CUE files.  Try turning that off in the Import settings.

Hi JimH,

Many thanks for your reply.

I will try using MC26 but I have bought Windows/Linux/MAC licenses for MC25, so I would rather stick with MC25 if possible. :-)

The file "\\MOZART\\MOZARTHolst - Cotswolds Symphony, Walt Whitman Overture, A Hampshire Suite March, The Perfect Fool Ballet Music, Scherzo for Orchestra (Douglas Bostock)\" indeed does not exist.

There is however a folder under the following directory: "\\MOZART\music\British Composers\Holst - Cotswolds Symphony, Walt Whitman Overture, A Hampshire Suite March, The Perfect Fool Ballet Music, Scherzo for Orchestra (Douglas Bostock)", with audio files inside.

So it does not seem normal that MediaCenter expects to find the file it reports as missing. Could it be the cause of the crashes ?

Finally, and as requested, I removed the .cue files from the auto-import settings. The program still crashes unfortunately. I know that sometimes the .cue file points to an incorrect .flac file but in this case, the program used to just report an error/exclusion at the end of the import process, not to crash.

Attached are the latest logs.

Many thanks,

OP
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #3 on: July 04, 2020, 05:37:00 pm »
Is it a crash (program disappears) or a freeze (program is unresponsive)?
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #4 on: July 04, 2020, 07:43:55 pm »
Quote from: JimH on July 04, 2020, 05:37:00 pm
Is it a crash (program disappears) or a freeze (program is unresponsive)?

A crash. The program window closes and the process disappears from task manager.
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #5 on: July 06, 2020, 04:36:05 pm »
Quote from: JimH on July 04, 2020, 01:04:40 pm
Could you try MC26?

UPDATE:

I installed a trial version of MC26 and indeed could not reproduce the crashes.

Kind regards,
OP
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #6 on: July 09, 2020, 02:41:54 am »
Hi again,

So I have uninstalled MC26 and installed back MC25 (version for which I own Linux/Windows/MAC licenses) and the problem persists.

The program is completely useless for me if I can't build a library so your help would be greatly appreciated.

Please let me know if any other information is needed.

Many thanks.

Best,
OP
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #7 on: July 09, 2020, 04:40:54 am »
UPDATE:

In case this is useful information: if the option "run auto import in the background" is checked, it seems that the library is (very) slowly built with no crash issue.

Regards,
OP
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #8 on: July 11, 2020, 04:43:06 am »
Quote from: JimH on July 04, 2020, 05:37:00 pm
Is it a crash (program disappears) or a freeze (program is unresponsive)?
Hi JimH

Do you need any other information ?

The program still crashes and I cannot build my music library. I specifically bought the license because of the library features (for mere playback of audio files, foobar does just fine).

Many thanks,

OP 
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7375
  • The color of Spring...
Re: Multiple crashes during auto import from network
« Reply #9 on: July 11, 2020, 06:05:43 am »
If it's crashing during import, you've probably got bad files causing it. The thing to do when this happens is to enable logging, then once it crashes open the logs and look towards the bottom of the log to see what file it last was trying to import, then move those file(s) to a location where MC won't try to import them and try importing in MC again and see if it gets past it.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #10 on: July 11, 2020, 08:29:25 am »
Quote from: Opawesome on July 06, 2020, 04:36:05 pm
UPDATE:

I installed a trial version of MC26 and indeed could not reproduce the crashes.

Kind regards,
OP
That's probably your easiest solution.

As Awesome Donkey said, we have seen bad files cause problems in the past.  When we can get the file, sometimes we can find a workaround. 
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #11 on: July 14, 2020, 01:14:46 pm »
Hi JimH,

Quote from: JimH on July 11, 2020, 08:29:25 am
That's probably your easiest solution.

Are you suggesting I should pay more money to have the program not crash ?

Quote from: JimH on July 11, 2020, 08:29:25 am
As Awesome Donkey said, we have seen bad files cause problems in the past.  When we can get the file, sometimes we can find a workaround.

What is the definition of a bad file ? Why would a file cause MC25 to crash upon import but not MC26 in the first place ? Can you please clarify ? I have like 100.000 files to import, I would need more details to identify the "bad file". Are you even sure the crash is caused by a particular file ? What in the 3 sets of logs I sent pointed you towards that direction ? 1 set of logs have not even been downloaded once...

And there is also the elephant in the room : why would I have to accept that "a bad file" (whatever, this means), can cause the program to just crash and be unusable. Is it not the software company's obligation to investigate and provide a fix ? Is there not some kind of warranty obligations when someone buys a software license but the program just crashes when he uses of the most basic function ?

It has been 10 days since I raised this issue, I have posted 8 messages, each with the debugging information asked (and even more), every time in a friendly manner, and frankly I am starting to feel that JRiver just does not care and that my problem will never get solved.

Kind regards,
OP   
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #12 on: July 14, 2020, 01:20:21 pm »
Corrupt might be a better description.
Logged

Opawesome

  • Recent member
  • *
  • Posts: 32
Re: Multiple crashes during auto import from network
« Reply #13 on: July 15, 2020, 08:42:40 am »
Quote from: JimH on July 14, 2020, 01:20:21 pm
Corrupt might be a better description.
This answer to my message is both rude and unacceptable.

What is the process to request a refund under the warranty obligation mentioned in the EULA please ?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #14 on: July 15, 2020, 09:16:56 am »
We don't provide refunds because we provide a 30 day trial.

You can probably work around your  problem by importing single file types (FLAC, for example) or single directories.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #15 on: July 15, 2020, 09:18:49 am »
You might find this useful:

https://yabb.jriver.com/interact/index.php/topic,81987.0.html

Also read the first post and the link there to antivirus problems.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #16 on: July 15, 2020, 09:30:08 am »
Search for "crash" in this thread:
https://yabb.jriver.com/interact/index.php/topic,81987.0.html

It has multiple pages.

You can reach me at jimh at jriver.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7375
  • The color of Spring...
Re: Multiple crashes during auto import from network
« Reply #17 on: July 15, 2020, 12:07:07 pm »
Quote from: Opawesome on July 15, 2020, 08:42:40 am
This answer to my message is both rude and unacceptable.

Well, regardless of the wording Jim used, it is basically what it is. What happens is sometimes files might be corrupted in some way, malformed in some way, etc. It's rare, but it does happen. Usually when such files are found users submit them to the developers and the crash issue gets fixed for the next build of MC. I'd say bad files are the most common reason for the majority of crashes reported, with antivirus incompatibilities being the second most common reason.

Quote from: JimH on July 15, 2020, 09:16:56 am
You can probably work around your  problem by importing single file types (FLAC, for example) or single directories.

Pretty much this. Unfortunately, MC25's development ended some time ago, so there's no more updates for it. It sounds like the crash you're experiencing was fixed sometime during the MC26 development cycle but if you wish to stick with MC25 what you basically need to do is what Jim said, import files in batches with logging enabled. If MC25 crashes anytime during this period open the logs and find the last file(s) MC25 was trying to import then move those file(s) out and see if importing progresses without crashing.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5175
  • "Linux Merit Badge" Recipient
Re: Multiple crashes during auto import from network
« Reply #18 on: July 15, 2020, 01:52:57 pm »
Quote from: Opawesome on July 15, 2020, 08:42:40 am
This answer to my message is both rude and unacceptable.

Just in case there is a misunderstanding here, Jim wasn't suggesting you were corrupt, but rather he was answering your question about what a "bad file" was.  His comment was saying that a "bad file" might better be described as corrupt (i.e. the file may have had its data corrupted) which is a neutral term, although certainly not much fun if the file was important:
https://en.wikipedia.org/wiki/Data_corruption

Logged

roognation

  • Regular Member
  • Junior Woodchuck
  • **
  • Posts: 92
  • Resistance is /dev/null
Re: Multiple crashes during auto import from network
« Reply #19 on: September 04, 2020, 01:12:12 pm »
Yeah, new install on a new workstation and just running in to this...  Where are the log files kept?
Logged
==
roognation
human electrode

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Multiple crashes during auto import from network
« Reply #20 on: September 04, 2020, 01:16:54 pm »
The wiki has a topic on logging.
Logged

roognation

  • Regular Member
  • Junior Woodchuck
  • **
  • Posts: 92
  • Resistance is /dev/null
Re: Multiple crashes during auto import from network
« Reply #21 on: September 04, 2020, 06:30:46 pm »
Found it.
C:\Users\[user]\AppData\Roaming\J River\Media Center 25\

not really sure anything looks bad?  Can anyone push me in the right direction?

Code: [Select]
10567485: 4964: Import: Process: Starting import (Media Center 25.0.115 (64-bit))
10567485: 4964: Import: GetNewFiles: Start
10567485: 4964: Import: GetNewFiles: Searching: D:\Ruger\Music\
10567500: 4964: Database: CDataHolderLookupMap::Load: Field: Filename; Elapsed ms: 4.477; Data bytes: 590584
10567500: 4964: Database: CDataHolder::Load: Field: Date Modified; Files: 15434; Pointer bytes: 123760; Data bytes: 32904; Elapsed ms: 0.537
10567500: 228: General: JRSuggestion::StopCategories: Start
10567500: 228: General: JRSuggestion::StopCategories: Finish (0 ms)
10567500: 228: General: JRSuggestion::StopCategories: Start
10567500: 228: General: JRSuggestion::StopCategories: Finish (0 ms)
10567500: 4964: Import: GetNewFiles: Searching: \\aai\Multimedia\Music\
10569219: 228: TV: CTVRecordingManager::Process: Start
10569219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10569219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10569219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9307905777222226 hours ago
10569219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10569219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10569860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Start
10569860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
10569860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
10571469: 228: Database: MCDB::Save: Start
10571469: 228: Database: MCDB::Save: Saving (bCleanDB: 0, bForce: 0)
10571469: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Library\field (date tagged).jmd
10571485: 228: Database: CDataHolder::Save: Field: Date Tagged; Elapsed ms: 10.616
10571485: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Thumbnails\{562037D5-3CCC-4323-B3EF-1F879F52553F}\Normal (v3)\field (thumbnail offset small).jmd
10571485: 228: Database: CDataHolder::Save: Field: Thumbnail Offset Small; Elapsed ms: 6.174
10571485: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Thumbnails\{562037D5-3CCC-4323-B3EF-1F879F52553F}\Normal (v3)\field (thumbnail offset medium).jmd
10571500: 228: Database: CDataHolder::Save: Field: Thumbnail Offset Medium; Elapsed ms: 6.364
10571500: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Thumbnails\{562037D5-3CCC-4323-B3EF-1F879F52553F}\Normal (v3)\field (thumbnail offset large).jmd
10571500: 228: Database: CDataHolder::Save: Field: Thumbnail Offset Large; Elapsed ms: 5.783
10571500: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Library\field (image width).jmd
10571500: 228: Database: CDataHolder::Save: Field: Image Width; Elapsed ms: 5.635
10571500: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Library\field (image height).jmd
10571516: 228: Database: CDataHolder::Save: Field: Image Height; Elapsed ms: 5.271
10571516: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Thumbnails\{562037D5-3CCC-4323-B3EF-1F879F52553F}\Normal (v3)\field (thumbnail info (local)).jmd
10571516: 228: Database: CDataHolder::Save: Field: Thumbnail Info (Local); Elapsed ms: 5.908
10571516: 228: Database: CPlaylistsDB::Save: Start
10571516: 228: Database: CPlaylistsDB::Save: Finish (0 ms)
10571516: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Library\browser.jmd
10571532: 228: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike Ruger\AppData\Roaming\J River\Media Center 25\Library\view state temporary (index).jmd
10571532: 228: Database: MCDB::Save: Finish (63 ms)
10574219: 228: TV: CTVRecordingManager::Process: Start
10574219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10574219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10574219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9321823941388892 hours ago
10574219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10574219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10579110: 228: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 3016
10579219: 228: TV: CTVRecordingManager::Process: Start
10579219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10579219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10579219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.933571129777778 hours ago
10579219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10579219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10584219: 228: TV: CTVRecordingManager::Process: Start
10584219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10584219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10584219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9349600729166672 hours ago
10584219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10584219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10589219: 228: TV: CTVRecordingManager::Process: Start
10589219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10589219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703766223, dialog days ago 0
10589219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.936346055194445 hours ago
10589219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10589219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10593328: 228: Podcast: CPodcastScheduler::Update: Start
10593328: 228: Podcast: CPodcastScheduler::Update: Processing completed work threads
10593328: 228: Podcast: CPodcastScheduler::Update: Purging files
10593328: 228: Podcast: CPodcastScheduler::Update: Scheduling downloads
10593328: 228: Podcast: CPodcastScheduler::ScheduleDownload: Start
10593328: 228: Podcast: CPodcastScheduler::ScheduleDownload: No work found
10593328: 228: Podcast: CPodcastScheduler::ScheduleDownload: Finish (0 ms)
10593328: 228: Podcast: CPodcastScheduler::Update: Finish (0 ms)
10594219: 228: TV: CTVRecordingManager::Process: Start
10594219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10594219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000566087910556, dialog days ago 0
10594219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9377344103055556 hours ago
10594219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10594219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10599219: 228: TV: CTVRecordingManager::Process: Start
10599219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10599219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10599219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9391231481666664 hours ago
10599219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10599219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10599860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Start
10599860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
10599860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
10604219: 228: TV: CTVRecordingManager::Process: Start
10604219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10604219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10604219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9405122171944446 hours ago
10604219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10604219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10609219: 228: TV: CTVRecordingManager::Process: Start
10609219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10609219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10609219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9419016298333332 hours ago
10609219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10609219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10614219: 228: TV: CTVRecordingManager::Process: Start
10614219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10614219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10614219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9432926849444442 hours ago
10614219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10614219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10619219: 228: TV: CTVRecordingManager::Process: Start
10619219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10619219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10619219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9446821766944446 hours ago
10619219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10619219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10624219: 228: TV: CTVRecordingManager::Process: Start
10624219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10624219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703766223, dialog days ago 0
10624219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9460683656944448 hours ago
10624219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10624219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10629219: 228: TV: CTVRecordingManager::Process: Start
10629219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10629219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10629219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9474571620833334 hours ago
10629219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10629219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10629860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Start
10629860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
10629860: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
10634219: 228: TV: CTVRecordingManager::Process: Start
10634219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10634219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10634219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9488484200833334 hours ago
10634219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10634219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10639219: 228: TV: CTVRecordingManager::Process: Start
10639219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10639219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10639219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.950234286722222 hours ago
10639219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10639219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10644219: 228: TV: CTVRecordingManager::Process: Start
10644219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10644219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10644219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9516259385833336 hours ago
10644219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10644219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10649219: 228: TV: CTVRecordingManager::Process: Start
10649219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10649219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10649219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9530156103055556 hours ago
10649219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10649219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10653438: 228: Podcast: CPodcastScheduler::Update: Start
10653438: 228: Podcast: CPodcastScheduler::Update: Processing completed work threads
10653438: 228: Podcast: CPodcastScheduler::Update: Purging files
10653438: 228: Podcast: CPodcastScheduler::Update: Scheduling downloads
10653438: 228: Podcast: CPodcastScheduler::ScheduleDownload: Start
10653453: 228: Podcast: CPodcastScheduler::ScheduleDownload: No work found
10653453: 228: Podcast: CPodcastScheduler::ScheduleDownload: Finish (15 ms)
10653453: 228: Podcast: CPodcastScheduler::Update: Finish (15 ms)
10654219: 228: TV: CTVRecordingManager::Process: Start
10654219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10654219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000553356512683, dialog days ago 0
10654219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9544044273333334 hours ago
10654219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10654219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10659219: 228: TV: CTVRecordingManager::Process: Start
10659219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10659219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703766223, dialog days ago 0
10659219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.955790570305556 hours ago
10659219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10659219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10659875: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Start
10659875: 228: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
10659875: 228: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
10664219: 228: TV: CTVRecordingManager::Process: Start
10664219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10664219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10664219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9571821817777776 hours ago
10664219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10664219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10669219: 228: TV: CTVRecordingManager::Process: Start
10669219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10669219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10669219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9585703271944448 hours ago
10669219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10669219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10674219: 228: TV: CTVRecordingManager::Process: Start
10674219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10674219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10674219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9599579708333334 hours ago
10674219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10674219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
10679219: 228: TV: CTVRecordingManager::Process: Start
10679219: 228: TV: CTVRecordingDatabase::GetActions: returning 0 actions
10679219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: Silent Days ago 0.0000578703693463, dialog days ago 0
10679219: 228: TV: CTVRecordingManager::PerformBackgroundTasks: checking program cleanup timer.  Last cleanup 2.9613452786944446 hours ago
10679219: 228: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
10679219: 228: TV: CTVRecordingManager::Process: Finish (0 ms)
Logged
==
roognation
human electrode
Pages: [1]   Go Up
« previous next »