INTERACT FORUM

Please login or register.

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

Author Topic: Import Problem  (Read 2035 times)

Point source

  • Recent member
  • *
  • Posts: 8
Import Problem
« on: October 03, 2018, 09:50:40 pm »
My 24.0.55 and the previous release are crashing on Win10 when running an import.
I have started using Chrome Canary in case it's a memory leak but no change.
How do i log a support ticket and upload my error log ?
Please note machine has not been used previously for JRiver and is reasonably spec'd..

System log is showing:
Application pop-up: Media Center 24.exe - Application Error : The instruction at 0x00007FFDFF714157 referenced memory at 0x0000000000000000. The memory could not be written.

Regards, Brian

I can confirm individual redbook folders can be imported and played thru a lumin D1.
Currently I have 5 albums loaded.
It's only when I select a top level folder holding hundreds of  albums that JR crashes.
Also can confirm last windows update in place.
Attaching last log file..
Logged

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10738
Re: Import Problem
« Reply #1 on: October 04, 2018, 05:54:57 am »
Please provide a log package following these instructions:
https://wiki.jriver.com/index.php/Logging
Logged
~ nevcairiel
~ Author of LAV Filters

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71498
  • Where did I put my teeth?
Re: Import Problem
« Reply #2 on: October 04, 2018, 06:20:52 am »
Is the program unresponsive?  Or does it disappear?  The first is a freeze.  The second is a crash.
Logged

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10738
Re: Import Problem
« Reply #3 on: October 04, 2018, 07:28:12 am »
It looks like you may be running out of memory while its trying to read some file tags. Which seems odd to me. But regardless I added a check to try to avoid that particular crash.
Logged
~ nevcairiel
~ Author of LAV Filters

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #4 on: October 04, 2018, 09:04:52 pm »
Quote from: JimH on October 04, 2018, 06:20:52 am
Is the program unresponsive?  Or does it disappear?  The first is a freeze.  The second is a crash.

Yep a crash it is.
Of note the album library has been treated with BLISS tagging software, so all tags have been filled.
Logged

~OHM~

  • Citizen of the Universe
  • *****
  • Posts: 1825
  • "I Don't Play The Music The Music Plays Me"
Re: Import Problem
« Reply #5 on: October 05, 2018, 01:11:35 am »
I took a look at Bliss...says it runs in the background....maybe stop that and see if you crash and burn....
Logged
“I've Reached A Turning Point In My Life. I Now Realize I Have More Yesterdays Then Tomorrows”

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #6 on: October 07, 2018, 01:31:07 am »
Quote from: ~OHM~ on October 05, 2018, 01:11:35 am
I took a look at Bliss...says it runs in the background....maybe stop that and see if you crash and burn....

Sorry i was commenting on pre- treatment of the files. I don't have Bliss running.

I am surprised that importing is becoming such an issue, also getting ' Skipped 113 files (filename too long).'
Surely a pre parse should be picking up likely errors during the import and dumping them out for me to do a manual workup.

Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71498
  • Where did I put my teeth?
Re: Import Problem
« Reply #7 on: October 07, 2018, 07:03:30 am »
Are you importing from a local drive or a NAS or a USB drive?
Logged

~OHM~

  • Citizen of the Universe
  • *****
  • Posts: 1825
  • "I Don't Play The Music The Music Plays Me"
Re: Import Problem
« Reply #8 on: October 07, 2018, 07:14:01 am »
Quote from: Point source on October 07, 2018, 01:31:07 am
I am surprised that importing is becoming such an issue, also getting ' Skipped 113 files (filename too long).'
Surely a pre parse should be picking up likely errors during the import and dumping them out for me to do a manual workup.
I import hundreds of files weekly and I have not seen any issues...sorry your having such a bad time!
Logged
“I've Reached A Turning Point In My Life. I Now Realize I Have More Yesterdays Then Tomorrows”

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #9 on: October 09, 2018, 06:57:24 pm »
Quote from: JimH on October 07, 2018, 07:03:30 am
Are you importing from a local drive or a NAS or a USB drive?

I don’t think it’s network related, in this case the files are on a local internal hard disk.
I’ll keep tinkering and do a couple of repeat imports after purging the library, to see whether I can identify what is going on.

Logged

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #10 on: October 14, 2018, 12:25:39 am »
Quote from: JimH on October 07, 2018, 07:03:30 am
Are you importing from a local drive or a NAS or a USB drive?

I just moved to another 'internal' drive and the import took 29,000 files and crashed three times as it ran out of memory.
None the less JR has pulled them in.

How do I FIND THE MISSING tracks that failed to import because of ' Skipped 113 files (filename too long).'
There are some pretty deep folder names but FreeFileSync or SynchToy manage long file names easily.
If I know what files are failing I can rename them, it could even be a hidden non standard character that is causing the overload.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71498
  • Where did I put my teeth?
Re: Import Problem
« Reply #11 on: October 14, 2018, 06:44:43 am »
Antivirus?
Logged

swiv3d

  • Guest
Re: Import Problem
« Reply #12 on: October 14, 2018, 03:20:36 pm »
You could try selecting support extra long filenames (experimental) under the tools>options>general>advanced tab to see if the long filenames will import. Might work - I can't say for sure
Logged

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #13 on: October 14, 2018, 06:55:13 pm »
Quote from: swiv3d on October 14, 2018, 03:20:36 pm
You could try selecting support extra long filenames (experimental) under the tools>options>general>advanced tab to see if the long filenames will import. Might work - I can't say for sure

Thanks will give it a shot.. any idea where the import error logs are?
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7411
  • The color of Spring...
Re: Import Problem
« Reply #14 on: October 15, 2018, 03:37:36 am »
You have to enable logging then reproduce the issue then look at the logs.

https://wiki.jriver.com/index.php/Logging
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2024 Update (24H2) 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) | iFi ZEN DAC 3 | Edifier R2000DB Bookshelf Speakers | Audio-Technica ATH-M50x Headphones

Point source

  • Recent member
  • *
  • Posts: 8
Re: Import Problem
« Reply #15 on: October 15, 2018, 06:07:41 am »
Quote from: Awesome Donkey on October 15, 2018, 03:37:36 am
You have to enable logging then reproduce the issue then look at the logs.

https://wiki.jriver.com/index.php/Logging

‘Seriously’ in any other mass import application, any failures would automatically be written to a separate import-failure log. This is not what I expect from a 2018 product or a 2006 product for that matter. And yes I have been exposed to multiple apps and import scenarios before I retired..
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71498
  • Where did I put my teeth?
Re: Import Problem
« Reply #16 on: October 15, 2018, 08:06:49 am »
Don't be crabby and pedantic.
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Import Problem
« Reply #17 on: October 15, 2018, 06:48:39 pm »
Quote from: Point source on October 14, 2018, 12:25:39 am
How do I FIND THE MISSING tracks that failed to import because of ' Skipped 113 files (filename too long).'

Just turn off background Auto Import (Uncheck "Options > Library & Folders > Auto-Import > Run auto import in background"), then run Auto Import manually. That should provide an "Import Summary" in the Action Windows area, with a "Details" button to click. In the Details windows that opens, any failed, skipped, or previously found bad files should be listed. The contents of that Details windows can be highlighted and copied, then pasted into some other App like Notepad so that you can review it and work through the issues. The contents of the Details window aren't stored when you close the windows by clicking Done. Of course, the information is still in the MC log as well, if you had that running.


While Hendrik has said it looks like you are running out of memory, I also think that is odd. I would at least run the Windows Memory Test function, and more likely run Memtest86+ for the recommended number of cycles, which I think is five or eight. That takes quite a while, but will root out memory issues. Even one failure is an indication of a problem with memory.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

alglove

  • Junior Woodchuck
  • **
  • Posts: 95
Re: Import Problem
« Reply #18 on: October 16, 2018, 05:32:54 pm »
If the file paths are longer than 260 characters, Windows may have trouble finding them. Fortunately, Windows 10 added a new feature that enables file paths up to 32767 characters long (give or take).

To enable it, go to the Windows Registry -->
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
On the right side, look for "LongPathsEnabled" (REG_DWORD) and set the value to 1

(I am not sure if you have to reboot, but I'd do it anyway, just to make sure the setting takes effect.)
(If you want to disable the setting, just go back and change the value to 0.)

https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/

This, combined with the setting suggested by swiv3d...
Quote from: swiv3d on October 14, 2018, 03:20:36 pm
You could try selecting support extra long filenames (experimental) under the tools>options>general>advanced tab to see if the long filenames will import. Might work - I can't say for sure

...may fix those "Skipped 113 files (filename too long)" errors.
Logged
Pages: [1]   Go Up
« previous next »