crashes while analyzing

ErikL's Avatar

ErikL

19 May, 2017 11:46 AM

Hi,

BT keeps crashing when analyzing (substantial number of) songs.
At first memory related crashes it seemed, with long intervals but now it crashes right away after displaying the splash screen.
There's plenty of mem allocated (8 GB at first, increased to 12 GB) System total 16. Win 10 pro.
Some crashes are accompanied by windows error msg about sys low on memory, but as far as I can see in Task Manager there is still headroom.

  1. Support Staff 1 Posted by hendrik on 19 May, 2017 12:04 PM

    hendrik's Avatar

    Hey Erik,

    A couple of questions:

    1. How many songs are in your library?
    2. Upon restart, has beaTunes ever offered to upload a crashlog?
    3. What exactly do you mean with "crash"? Did the application freeze (not react to input) or simply "disappear"?
    4. After beaTunes crashed, did you kill it via the Task Manager?

    Thank you,

    -hendrik

  2. 2 Posted by ErikL on 19 May, 2017 12:16 PM

    ErikL's Avatar

    Thanks for the quick reply.

    1. total 200.000+. Yesterday afternoon I started analyzing a batch of appx 15k songs. Went well for a couple of hrs, then had 3 crashes with long intervals and then it chugged along happily all night. This morning more crashes culminating in not getting past the splash screen.

    2. nope

    3/4. disappear, also from task manager.

  3. Support Staff 3 Posted by hendrik on 19 May, 2017 12:42 PM

    hendrik's Avatar

    Thank you for the info.

    In C:\Users\naglag\AppData\Local\Temp, C:\Program Files\beaTunes4\ or any of its subdirectories, is there a file starting with the name hs_err_?
    Or perhaps in your home directory C:\Users\naglag?

    If you can find such a file, can you please send it to me?

    Thanks,

    -hendrik

  4. 4 Posted by ErikL on 19 May, 2017 01:11 PM

    ErikL's Avatar

    Found some in the temp dir and had a look. Seems to be consistent with the windows error msg I saw, so probably not a Beatunes issue.
    As I said in the OP total memory was never maxed out, but I don't claim to understand all the metrics in task manager's memory tab.

    It's probably a bit extreme to commit a batch of 15k files for analysis, but who knows it might help with further improving memory mgt :-)

  5. Support Staff 5 Posted by hendrik on 19 May, 2017 01:17 PM

    hendrik's Avatar

    In any case...

    I took a look at your logs. From what I can tell, 12GB are overkill and may contribute to the trouble you're having. Please reduce that back to 8GB. If you're unsure about memory, please open the beaTunes About dialog. It lets you monitor beaTunes' memory consumption. (your logs don't really show more than 4GB use).

    Also, please shut down beaTunes and download and install the current dev snapshot from https://www.beatunes.com/download/beaTunes-4-6-16-SNAPSHOT-x64.exe

    It contains a code change that may solve the original problem you were experiencing. Please give this a try and let me know how it goes. Should there still be issues, please send fresh logs.

    That all aside, here's a little tip for running the analysis with a very large collection:

    Whenever you are calculating a value (e.g. BPM), beaTunes will check whether it needs to be displayed in the main table. If the main table it set to show all your 200K songs, this may require reloading the complete 200K index to do proper sorting & ordering.

    So to ease the workload, create an empty playlist and make sure it's shown during analysis. Also, and this may not really make a difference, make sure the sort order of the main table is set to something that has nothing to do with the analyzed properties, e.g. grouping.

    Thanks,

    -hendrik

  6. Support Staff 6 Posted by hendrik on 19 May, 2017 01:20 PM

    hendrik's Avatar

    Thanks for those logs.

    Found some in the temp dir and had a look.

    Which one? C:\Users\naglag\AppData\Local\Temp?

    These logs support the hypothesis that your system does not support granting beaTunes the 12GB you said it should allocate. Reducing to 8GB is probably the best bet.

  7. 7 Posted by ErikL on 19 May, 2017 01:30 PM

    ErikL's Avatar

    Which one? C:\Users\naglag\AppData\Local\Temp? yep

    Thanks for the tips. it's very helpful to have some insight into the internals.
    I'll need some time to go through it.

  8. Support Staff 8 Posted by hendrik on 19 May, 2017 04:06 PM

    hendrik's Avatar

    Which one? C:\Users\naglag\AppData\Local\Temp

    yep

    Thanks. I will need to change the the crash log reporting to take that into account.

  9. 9 Posted by ErikL on 20 May, 2017 09:37 AM

    ErikL's Avatar

    This comment was split into a new discussion: Problem with super large FLAC, 88200.0 Hz, 24 bit, 6 channels, 18 bytes/frame, little-endian

    Whenever you are calculating a value (e.g. BPM), beaTunes will check whether it needs to be displayed in the main table. If the main table it set to show all your 200K songs, this may require reloading the complete 200K index to do proper sorting & ordering.

    to ease the workload, create an empty playlist and make sure it's shown during analysis

    Is this regardless of whether the main table is visible (library tab in focus)?

    make sure the sort order of the main table is set to something that has nothing to do with the analyzed properties

    It was set to COLOR because that was the only way I know to select unanalyzed songs. So if this makes a difference it will have contributed.

    RESULTS
    I did a analyze-run with the new snapshot and empty playlist in library view. Analyzing is about 3x as fast as it was before. Now the CPU consistently maxes out and BT remains responsive during analysis.

    In the memory tab of task manager the left value in the "Committed" pair is much lower than before. Both values used to be within 1-2 GB, now there's a spread of 8 GB.

    So a great improvement, thanks.

    There was a file-related issue:
    The last msg in the bottom pane of the Analisys tab was
    "Failed to decode track 'Our Delight' (java.lang.IllegalArgumentException: Failed to create AudioInputStream with format PCM_SIGNED 88200.0 Hz, 24 bit, 6 channels, 18 bytes/frame, little-endian from com.tagtraum.ffsampledsp.FFAudioInputStream@7b9f97a8)".

    I think BT broke off analysis there. It's a 370 MB flac file, so I can't upload it. Foobar and JRiver play it OK, but BT errors with msg "failed to open item. Unrecognized file signature"

    EDIT: error while uploading logs (413)

  10. Support Staff 10 Posted by hendrik on 20 May, 2017 10:30 AM

    hendrik's Avatar

    to ease the workload, create an empty playlist and make sure it's shown during analysis

    Is this regardless of whether the main table is visible (library tab in focus)?

    Yes.

    So a great improvement, thanks.

    My pleasure.

    There was a file-related issue: The last msg in the bottom pane of the Analisys tab was
    "Failed to decode track 'Our Delight' (java.lang.IllegalArgumentException: Failed to create AudioInputStream with format PCM_SIGNED 88200.0 Hz, 24 bit, 6 channels, 18 bytes/frame, little-endian from com.tagtraum.ffsampledsp.FFAudioInputStream@7b9f97a8)".

    I think BT broke off analysis there. It's a 370 MB flac file, so I can't upload it. Foobar and JRiver play it OK, but BT errors with msg "failed to open item. Unrecognized file signature"

    EDIT: error while uploading logs (413)

    Please start separate discussion for separate topics. I'm going to split this last one of..

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • logs.zip 4.59 MB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac