INTERACT FORUM

Please login or register.

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

Author Topic: Continuing to Have Problems With Handheld Sync from Client  (Read 7497 times)

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Continuing to Have Problems With Handheld Sync from Client
« on: November 15, 2010, 09:21:13 pm »
Tried to sync to my handheld tonight (a folder on drive C) using my HTPC (connected to the library server machine in the basement).  CPU Usage fluctuated, but was often 50-60% on a Quad Core CPU, especially at the beginning of the process.  MC crashed after about 15-20 minutes.  Log:

http://glynor.com/temp/Handheld_Sync_Log.zip
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #1 on: November 15, 2010, 09:51:46 pm »
I do wonder if it is related to this: http://yabb.jriver.com/interact/index.php?topic=60503.0

Would it help to have a corresponding log from the Library Server itself?  Does it log when it is running in the notification tray, or does the full UI need to be running?
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #2 on: November 15, 2010, 10:04:57 pm »
I tried it again, and this time it synced correctly without crashing or misbehaving.  CPU Usage was much more reasonable 20-40% for most of the time I monitored it.

The only thing I did differently was I navigated away from the Sync list in MC (just to my default Audio View) just after starting the sync.  The original time, before it crashed, I'd left it sitting on the sync list view (which was updating and showing the status of each file) and minimized the application.

I feel like the other times I've had trouble, I was always using it showing the sync list when it crashed.  I don't absolutely know this for sure though.  I often sync with that list up though.

Anyhow... It is a wild shot in the dark, but could the bug be in syncing with a Library Server Client while watching the updating sync-list view?
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #3 on: November 16, 2010, 02:08:10 pm »
Quote from: glynor on November 15, 2010, 09:51:46 pm
Would it help to have a corresponding log from the Library Server itself?
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

JohnT

  • Citizen of the Universe
  • *****
  • Posts: 4627
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #4 on: November 17, 2010, 02:47:03 pm »
Is it doing conversion of Flac files?
Logged
John Thompson, JRiver Media Center

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #5 on: November 17, 2010, 04:08:45 pm »
Mostly high-bitrate MP3s to low-bitrate MP3s, but yes, it is also doing FLAC conversions.  Probably 1/5-1/6th of my music library is FLAC, spread throughout.

The way my "handheld" is set up is with a set of playlists.  The "main mix" playlist pulls from the full music library, excludes some tracks (based on ratings and other tags), then does a ~mix command on it to generate a list that matches certain Genres in certain proportions.  So, each sync is different than the last.

There is no easy way for me to test my existing handheld without FLAC files, without excluding them.  If I exclude them, then most of my "good" music (which is what I've bothered to rip in FLAC) would be excluded.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #6 on: November 18, 2010, 12:28:31 pm »
Bump, since Jim locked the other one.  This is still an issue.  It crashed on me last night again.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

JohnT

  • Citizen of the Universe
  • *****
  • Posts: 4627
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #7 on: November 18, 2010, 12:37:14 pm »
Is there any way you could devise a test to prove that it's either a Flac conversion issue or a general conversion issue?  This would narrow it down a heck of a lot for us.  If it never crashes with a strictly non-Flac filelist but crashes every time when Flacs are mixed in, that would tell us a lot.
Logged
John Thompson, JRiver Media Center

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #8 on: November 18, 2010, 02:13:41 pm »
Testing now.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #9 on: November 18, 2010, 02:31:54 pm »
I just converted a bunch of files to APE for testing purposes.  The one problem I envisioned is that if I exclude all the FLAC files, that doesn't leave many conversions other than MP3<>MP3.  I have a few other misc music file types in my library, but most of those would be excluded on their own for other reasons, or would have already been converted.  So... My solution is that I'm excluding all FLAC files from my main sync list, and manually adding in the APE files.  That should give me a good test, since all the APE files are brand new and won't have any conversion cache files created already.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #10 on: November 18, 2010, 02:46:46 pm »
No crash yet (but it isn't that far in yet), but ALL of my image files are not syncing over (they simply list "error").  No reason as to why.  If I switch to connecting to the Library directly, these work fine.


Click to enlarge

Sorry about the distortion in the screen capture.  I'm doing this from the office via VNC, and the screen was updating too fast for the VNC client.  This isn't how it actually looks on screen, of course.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #11 on: November 18, 2010, 03:35:18 pm »
The sync finished without crashing.  Of course, it works some times seemingly without reason.  However, that is a pretty good sign.  I put my sync list back to normal (which should include a few FLAC files at least) and I'm trying again.

Just so you know, regarding the Image error issue... Sometimes they work fine, and other times they error, seemingly without rhyme or reason.  Like this:



As you can see... Some are listing "error" while others, taken with the same camera at the same time in the same folder location, work just fine.  Frustrating, and really irritating that we get no feedback other than "error".
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

JohnT

  • Citizen of the Universe
  • *****
  • Posts: 4627
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #12 on: November 18, 2010, 03:52:57 pm »
I'm testing image transfer now - from your report it looks like something weird is going on there.
Logged
John Thompson, JRiver Media Center

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #13 on: November 18, 2010, 04:38:49 pm »
If it matters, I do have a custom image resize set.  I don't remember the exact dimensions but I can get it for you shortly.

EDIT: 3600x2400.

My second test also succeeded.  However, I suspect that many of my synced FLAC files now have already been conversion cached, and there were no new images at all.

I can nuke my conversion cache and try again, if you think it would help.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #14 on: November 19, 2010, 11:19:47 am »
I'm testing again today, as my time permits, with some changes... I deleted my entire audio conversion cache (again), and I also removed everything that already existed in my "handheld" folder.  I'm doing a "standard" sync (including some FLAC files) first.  We'll see how it goes...

PS. I should add... The list view updating performance seems DRAMATICALLY improved with the new build.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #15 on: November 19, 2010, 01:25:07 pm »
Okay.  I'm not sure if this is good news or bad news, but I got another crash on my test.  Want the log?

I'm going to "reset" it back (delete the cache and synced files) and try again with it in "no flac" mode and see if I can get a crash.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #16 on: November 19, 2010, 01:52:16 pm »
Okay... The "Phase 2" test sync is running now (no FLAC files).  We'll see.  FYI:  I eliminated FLAC, but there are still M4A and WMA files in the sync list (the WMAs will be converted to MP3), in addition to my "tester" APE files I made.

If you want the log from the first test, which crashed, just let me know.  I have it saved.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42373
  • Shoes gone again!
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #17 on: November 19, 2010, 03:28:39 pm »
We believe these problems will be fixed in a coming build.

The UI was getting buried under progress messages from the downloading of images (that go from 0 to 100 in a fraction of a second on a LAN).
Logged
Matt Ashland, JRiver Media Center

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #18 on: November 19, 2010, 03:32:10 pm »
It does NOT appear to be FLAC related.  It just crashed again on that second test sync, which had absolutely ZERO FLAC files included.  It is hard to tell, but it looks like it was actually working on "uploading" a MP3 file at the time of the crash.


Click to enlarge

I'm also including a screenshot showing my settings used for this sync:


Click to enlarge.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #19 on: November 19, 2010, 03:32:56 pm »
Quote from: Matt on November 19, 2010, 03:28:39 pm
We believe these problems will be fixed in a coming build.

The UI was getting buried under progress messages from the downloading of images (that go from 0 to 100 in a fraction of a second on a LAN).

Oh, awesome!  Thanks, guys!
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #20 on: November 19, 2010, 10:45:58 pm »
Updated to the new build.  Still crashed just like before.  Didn't notice if the image errors still occurred, since I wasn't actually watching it "live" during the test sync.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #21 on: November 19, 2010, 10:56:03 pm »
I'm trying the transfer again.  I went through and deleted my existing audio files in the handheld sync folder.

It seems like the time-to-completion estimation has changed.  It is a LOT more optimistic early on than it was before.  When I did my tests earlier today (with the previous build), it would generally list 2-2.5 hours to completion pretty quickly after starting.  It wouldn't actually ever take quite that long (though it would take a long time, and much longer than it would take with a direct connection to the library).  It would generally get down to around 1 hour remaining, and then would suddenly jump to complete.

This time, it started off listing 18-20 minutes.  It has been running about 20 minutes, and now it lists 58 minutes remaining.  That's actually more in-line with what I saw with directly connected syncs, though still maybe slightly slower.

The bitrate throughput listed fluctuates a lot, but generally seems substantially higher than it was with previous builds, so I think it is actually doing the sync faster.  With previous builds, I was seeing typical speeds of 60-80MB/s, with occasional fluctuations up to 100MB/s or so (and occasional stalls down to 20-30).  Now it seems like it is staying up around 100MB/s a lot more, and fluctuating wildly (often showing as high as 160MB/s).  Of course, it always slows way down when it has to actually convert a track, and is fast when it can use a cached or direct file.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #22 on: November 19, 2010, 11:42:58 pm »
It crashed.  The "estimate to completion" was around 32 minutes.  Here is the tail from the log:

Code: [Select]
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Start
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\13 - the downward spiral.mp3
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Opening input file
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Analyzing input file
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Creating output filename and path
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Creating output file
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Allocating space for file
2242499: 2760: Handheld: CPortableDriveBase::TransferFile: Starting transfer loop
2242499: 2760: Handheld: CPortableDriveBase::TransferFile:     Reading 7337955 bytes
2242499: 2760: Handheld: CPortableDriveBase::TransferFile:     Writing 4634764 bytes
2242515: 2760: Handheld: CPortableDriveBase::TransferFile:     Sending progress
2242515: 2760: Handheld: CPortableDriveBase::TransferFile:     EOF
2242515: 2760: Handheld: CPortableDriveBase::TransferFile: Finished transfer
2242515: 2760: Handheld: CPortableDriveBase::TransferFile: Finish (16 ms)
2242515: 2760: Handheld: CPortableDriveGeneric::Upload: Finish (16 ms)
2242515: 2760: Handheld: CHHPluginThread::Thread Message Processing: Finish (16 ms)
2242530: 5812: Handheld: CHHUploadWorker::NotifyDownloadFinished: Start
2242530: 5812: Import: JRAnalyzer::Open: Start
2242530: 5812: Import: JRAnalyzer::AddFile: Start
2242530: 5812: Import: JRAnalyzer::AddFile: Filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\14 - hurt.mp3
2242530: 5812: Import: JRAnalyzer::AddFileMJ: Start
2242530: 5812: Import: JRAnalyzer::AddFileMJ: Finish (0 ms)
2242530: 5812: Import: JRAnalyzer::AddFile: Finish (0 ms)
2242530: 5812: Import: JRAnalyzer::Open: Finish (0 ms)
2242530: 5812: Database: JRAnalyzerFile::GetImage: Start
2242530: 5812: Database: JRAnalyzerFile::GetImage: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::StartNextUpload: Start
2242530: 5812: Handheld: CHHUploadWorker::StartNextUpload: Already uploading, nothing to do
2242530: 5812: Handheld: CHHUploadWorker::StartNextUpload: Finish (0 ms)
2242530: 5812: Handheld: CHHUploadWorker::NotifyDownloadFinished: Finish (0 ms)
2242546: 800: Handheld: CHHPluginThread::ProcessCommand: Finish (47 ms)
2242546: 800: Handheld: CHHUploadWorkerUploadThread::Thread: Upload complete (hr=0)
2242546: 800: Handheld: CHHUploadWorkerUploadThread::Thread: Cleaning up
2242546: 800: Handheld: CHHUploadWorkerUploadThread::Thread: Finish (47 ms)
2242561: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Start
2242561: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Setting status
2242561: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Deleting upload thread
2242561: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Starting next upload
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::StartNextUpload: Start
2242561: 5812: Handheld: CHHUploadWorker::StartNextUpload: Uploading file 2889
2242561: 5812: Handheld: CHHUploadWorker::StartNextUpload: Starting upload thread
2242561: 5812: Handheld: CHHUploadWorker::StartNextUpload: Finish (0 ms)
2242561: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Finish (0 ms)
2242561: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Start
2242561: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Creating file object (filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\14 - hurt.mp3)
2242561: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Sending upload command
2242561: 2460: Handheld: CHHPluginThread::ProcessCommand: Start
2242561: 2760: Handheld: CHHPluginThread::Thread Message Processing: Start
2242561: 2760: Handheld: CHHPluginThread::Thread Message Processing: Type: 0, Function: 2
2242561: 2760: Handheld: CHHPluginThread::Thread Message Processing: Command = 1025
2242561: 2760: Handheld: CPortableDriveGeneric::Upload: Start
2242561: 2760: Handheld: CPortableDriveBase::GetBasePathFromFile: Start
2242561: 2760: Handheld: CPortableDriveBase::GetBasePathFromFile: Finish (0 ms)
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Start
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\14 - hurt.mp3
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Opening input file
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Analyzing input file
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Creating output filename and path
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Creating output file
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Allocating space for file
2242561: 2760: Handheld: CPortableDriveBase::TransferFile: Starting transfer loop
2242561: 2760: Handheld: CPortableDriveBase::TransferFile:     Reading 7338215 bytes
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     Writing 7338215 bytes
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     Sending progress
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     Reading 7338442 bytes
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     Writing 332134 bytes
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     Sending progress
2242577: 2760: Handheld: CPortableDriveBase::TransferFile:     EOF
2242577: 2760: Handheld: CPortableDriveBase::TransferFile: Finished transfer
2242577: 2760: Handheld: CPortableDriveBase::TransferFile: Finish (16 ms)
2242577: 2760: Handheld: CPortableDriveGeneric::Upload: Finish (16 ms)
2242577: 2760: Handheld: CHHPluginThread::Thread Message Processing: Finish (16 ms)
2242608: 2460: Handheld: CHHPluginThread::ProcessCommand: Finish (47 ms)
2242608: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Upload complete (hr=0)
2242608: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Cleaning up
2242608: 2460: Handheld: CHHUploadWorkerUploadThread::Thread: Finish (47 ms)
2242624: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Start
2242624: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Setting status
2242624: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Deleting upload thread
2242624: 5812: Handheld: CHHUploadWorker::NotifyUploadFinished: Starting next upload
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
2242624: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242624: 5812: Handheld: CHHUploadWorker::StartNextConversion: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
2242624: 5812: Handheld: CHHUploadWorker::StartNextUpload: Start
2242624: 5812: Handheld: CHHUploadWorker::StartNextUpload: Done with all uploads -- starting next stage
2244246: 5812: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
2244246: 5812: General: TopLevelExceptionFilter: Message: 34768, wParam: 194652464, lParam: 0, Window class: Thread Notification Window Class - 0x2D574DC0
Interestingly, it lists "Handheld: CHHUploadWorker::StartNextUpload: Done with all uploads -- starting next stage" and then crashes immediately.  This matches exactly what happened earlier with build 156:
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #23 on: November 19, 2010, 11:43:08 pm »
Code: [Select]
4580221: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Start
4580221: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Creating file object (filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\13 - the downward spiral.mp3)
4580221: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Sending upload command
4580221: 5736: Handheld: CHHPluginThread::ProcessCommand: Start
4580221: 1800: Handheld: CHHPluginThread::Thread Message Processing: Start
4580221: 1800: Handheld: CHHPluginThread::Thread Message Processing: Type: 0, Function: 2
4580221: 1800: Handheld: CHHPluginThread::Thread Message Processing: Command = 1025
4580221: 1800: Handheld: CPortableDriveGeneric::Upload: Start
4580221: 1800: Handheld: CPortableDriveBase::GetBasePathFromFile: Start
4580221: 1800: Handheld: CPortableDriveBase::GetBasePathFromFile: Finish (0 ms)
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Start
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Filename: C:\Users\glynor\AppData\Roaming\J River\Media Center 15\Temp\13 - the downward spiral.mp3
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Opening input file
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Analyzing input file
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Creating output filename and path
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Creating output file
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Allocating space for file
4580221: 1800: Handheld: CPortableDriveBase::TransferFile: Starting transfer loop
4580221: 1800: Handheld: CPortableDriveBase::TransferFile:     Reading 7333455 bytes
4580221: 1800: Handheld: CPortableDriveBase::TransferFile:     Writing 4587520 bytes
4580236: 1800: Handheld: CPortableDriveBase::TransferFile:     Sending progress
4580236: 1800: Handheld: CPortableDriveBase::TransferFile:     EOF
4580236: 1800: Handheld: CPortableDriveBase::TransferFile: Finished transfer
4580236: 1800: Handheld: CPortableDriveBase::TransferFile: Finish (15 ms)
4580236: 1800: Handheld: CPortableDriveGeneric::Upload: Finish (15 ms)
4580236: 1800: Handheld: CHHPluginThread::Thread Message Processing: Finish (15 ms)
4580268: 5736: Handheld: CHHPluginThread::ProcessCommand: Finish (47 ms)
4580268: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Upload complete (hr=0)
4580268: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Cleaning up
4580268: 5736: Handheld: CHHUploadWorkerUploadThread::Thread: Finish (47 ms)
4580283: 5544: Handheld: CHHUploadWorker::NotifyUploadFinished: Start
4580283: 5544: Handheld: CHHUploadWorker::NotifyUploadFinished: Setting status
4580283: 5544: Handheld: CHHUploadWorker::NotifyUploadFinished: Deleting upload thread
4580283: 5544: Handheld: CHHUploadWorker::NotifyUploadFinished: Starting next upload
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextDownload: Finish (0 ms)
4580283: 5544: Handheld: CHHUploadWorker::StartNextConversion: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
4580283: 5544: Handheld: CHHUploadWorker::StartNextConversion: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextConversion: Finish (0 ms)
4580283: 5544: Handheld: CHHUploadWorker::StartNextUpload: Start
4580283: 5544: Handheld: CHHUploadWorker::StartNextUpload: Done with all uploads -- starting next stage
4580392: 5544: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
4580392: 5544: General: TopLevelExceptionFilter: Message: 1025, wParam: 1, lParam: 0, Window class: JRiver Bar Class
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #24 on: November 20, 2010, 12:45:22 am »
It might not be related, but it sure could be... I just found this in my "By Disk Location" view.


Click to enlarge

The names of the files look similar to ones I've seen "late" in the sync crash logs that I've looked at.  I've been checking those for patterns to see if I can find bad files and eliminate them.  I can't be sure that they all are, but I know I've seen at least a few of them.

These broken files are all on the C drive in MC's temp location, and are all broken.  I certainly never imported these files myself, and the AppData folders are not monitored by Auto-Import.

Think they could be the remnants of the crashing transfers?  The files themselves are gone.  Neither client or server have them (though I do have a bunch of Delta.zip files and FLAC image files in the Temp folder on my server).
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #25 on: November 20, 2010, 07:17:06 am »
glynor,
Could they be part of the stacks issue from a couple weeks ago?  Try right clicking and "repair stacks" if so.
Logged

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #26 on: November 20, 2010, 11:15:19 am »
No.  They're definitely part of the sync process.  Look at that file name in the image above.  They're in MC's temp directory, and the filenames are things like "AudioStream - 780".  My stacks have been behaving fine since the fix (and I repaired them all via that tool after the bad build).

But, before I went to bed, I did one last test.  I deleted them all from the library, did a new sync (which crashed), and I had a bunch of new ones.  I actually expected only one, but I ended up with a bunch, which was curious.
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2661
Re: Continuing to Have Problems With Handheld Sync from Client
« Reply #27 on: January 18, 2011, 06:28:33 pm »
I'm having these same issues syncing my handheld over the library client. It keeps bringing down MC with it, and I'll also get random "points to the wrong file location" errors.
Logged
Pages: [1]   Go Up
« previous next »