Core Machine (Operating system/System info/Roon build number)
Windows 10 Home
Intel Core i7-8700 CPU @ 3.20 GHz, 64-Bit OS
running Roon Core Version 1.7 (build 710)
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Music is stored on a QNAP NAS. Roon Core and NAS are both hardwired to the router via Ethernet.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Description Of Issue
I recently moved a bunch of files around on my server and decided to do a fresh import of my music content in Roon. I’ve successfully used Roon to Re-Scan and Re-Import my huge library, but it keeps crashing while scanning one particular folder, “Jazz.” If I disable that folder, everything works fine.
In this video, you can see Roon crash as the scanner hits 67358 files in the “jazz” folder. FYI This folder contains about 120,000 music files, all neatly organized like [artist]/[Album]/[Disc#]-[Track #]. [name]. Roon has had no trouble indexing this content in the past, and it is having no trouble with other folders of similar sizes on my NAS.
I suspect there’s a corrupt or incompatible file in that folder, but I have no idea how to find out which one it is. Is there any log that can tell me where Roon is getting stuck so I can take a look at the file(s) that are causing problems? I just reproduced the problem, causing Roon to crash. Logs here: https://drive.google.com/file/d/197UO__RzsIWgqyFocC-q-8OMFwWyIi_j/view?usp=sharing
@Support did you get a chance to check these logs? Any clues?
@dylan @noris can somebody take a look at this please when you have a minute? Any tips? Thanks!
Apologies for the delay here! We took a look at the logs but unfortunately we didn’t see anything that jumped out as an issue right away. Can you reproduce this issue once more and the next time it occurs let us know the specific time? We’ll enable diagnostics and analyze that specific event with our QA team.
Hey @dylan thanks so much for getting back to me on this. Yes, I will replicate it now. Do you want me to resend the logs after doing so?
@Dylan just replicated the issue at 3:02 pm MST.
I replicated it by re-enabling the “Jazz” storage folder, which I had temporarily disabled as scanning that folder consistently causes a fatal crash.
Hello @Ari_Margolis, I have gone ahead and enabled diagnostics mode for your account and what this action will do is next time your Core is active, a set of logs will automatically be generated and uploaded to our servers for analysis. From there, I will send the information over to our QA team for further analysis.
BTW - it’s inexcusable that bad data crashes a program.
@nuwiry I just started Roon Core and it crashed again, same as before. Kindly let me know if you received the logs?
Hello @Ari_Margolis, I see the activity but for some reason, the diagnostic didn’t come in. Could you please use the directions found here and send us over a set of logs using a shared Dropbox link.
With the timestamps and the previous logs you sent over, I’ve got everything packaged up and sent it over to the QA team for their input.
@nuwriy I hope you had a good weekend. Any update from QA?
Apologies for the delay, @Ari_Margolis. @nuwriy is out of the office today but we’ve passed the logs along and have a meeting scheduled with our QA team to discuss folder. We’ll follow up as soon as we’ve met with them. Thanks!
Hello @Ari_Margolis, and thanks for your patience while the team discussed the issue. TO help them with their investigation, could you please send us a copy of the following?
- Press Win + R and type eventvwr.msc
OK – this should open
Event Viewer window
- From the left sidebar go to Windows Logs > Application
- Right click on the
Application subsection and pick
Filter Current Log... from the context menu
- On the
Filter tab for the
Logged section pick a parameter
Last 30 days and press
- Right-click on the Application subsection again and pick
Save filtered log file as.. from the context menu
- Enter the log file name, for e.g.
Roon_USERNAME , and press
- Upload the Event Viewer logs to our diagnostics servers, information has been sent via private message
@dylan @nuwriy sorry, I missed this until today! I just updated the logs as requested, after replicating the issue once more. I also included a video of what the crash looks like.
Hello @Ari_Margolis, and thanks for uploading that! I’ve passed this info along to the QA team and I’ll update you once I have their feedback.
Hello @Ari_Margolis, and thanks for your patience while the QA team reviewed the data we sent over. We believe we have identified the tracks causing the issue, could you please remove the following items and try scanning the folder again?
01/13 09:26:32 Trace: [metadatasvc] GOT  (133ms) Sooloos.Msg.Metadata.GetMetadataResponse:
01/13 09:26:32 Trace: [metadatasvc] GOT  (299ms) Sooloos.Msg.Metadata.GetMetadataResponse:
01/13 09:26:32 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\03. You Know Me.wav
01/13 09:26:32 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\04. Tubby.wav
01/13 09:26:32 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\01. Grendel.wav
01/13 09:26:32 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\02. Tight Rope.wav
01/13 09:26:32 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\05. Dig To China.wav
01/13 09:26:32 Info: [updatemetadata] advancing metadata timestamp on 56 tracks
01/13 09:26:33 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\06. Becky's Bash.wav
01/13 09:26:33 Trace: [library/compute] computing 1 tracks
01/13 09:26:33 Trace: [dbperf] flush 505404 bytes, 357 ops in 183 ms (cumulative 2427611 bytes, 1058 ops in 72756 ms)
01/13 09:26:33 Trace: [storage] [directory] extracting V:\Jazz\Ted Sorita's Rebel Souls\vs The Forces Of Evil [24,96]\07. Impengu Dek Bengikai.wav
01/13 09:26:33 Trace: [library] finished with 16139 dirty tracks 893 dirty albums 3682 dirty performers 6087 dirty works 10379 dirty performances 341 dirty genres 0 clumping tracks, 0 clumping auxfiles 1 compute tracks, 0 deleted tracks, 56 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 24425 changed objects
01/13 09:26:33 Trace: [library] endmutation in 464ms
@nuwriy I deleted those files, but it is still crashing just like before.
I decided to switch cores back to a dedicated computer which on which I previously ran roon for years with no major issues like that. After upgrading to 1.8 and then re-importing the library on the old computer, it is still crashing.
Here are the details of the new computer running Core:
I have the event logs and I can upload them to you but that link you sent expired.
@nuwriy @dylan any further ideas? I would hate to have to omit my entire “jazz” folder from my library just to get roon to run without crashing.
Hello @Ari_Margolis ,
Can you please upload the new logs to the link I sent you via private message? Thanks!