BeaTunes Fatal Error

Jack Ellis's Avatar

Jack Ellis

11 Aug, 2010 09:05 PM

BeaTunes 2.1.11 Fatal Error message:
The Java VM ran out of memory.

System info.
12256 tunes.
Windows 7 Ultimate - 64bit
4.0 GB memory. Intel Q9450

  1. Support Staff 1 Posted by hendrik on 11 Aug, 2010 10:22 PM

    hendrik's Avatar

    Hi Jack,

    please restart beaTunes and check in the Preferences (Edit menu), subtab Analysis, what the number of analysis tasks is set to. You might want to reduce that to 2, if it's higher than 2.

    -hendrik

  2. 2 Posted by Jack on 12 Aug, 2010 12:12 AM

    Jack's Avatar

    After multiple restarts and a computer reboot, I looked at the Task Queue and noticed it was trying to Analyze 3 files of an Audio Book which were an hour and 16 min each. When it got past those the problem went away. I have tried to remove my audio books from the Analysis process. This makes sense to me as to why Java ran out of memory, which isn't really your problem anyway. I was trying to have it Analyze my entire Library. I have removed the audio books and podcast from the process, and have not had a repeat of the fatal error.
    Thank you for your attention to my problem and swift response.

    Sincerely,

    Jack Ellis
    [email blocked]

    -----Original Message-----
    From: hendrik [mailto:[email blocked]]
    Sent: Wednesday, August 11, 2010 17:25
    To: [email blocked]
    Subject: Re: BeaTunes Fatal Error [Problems]

  3. Support Staff 3 Posted by hendrik on 12 Aug, 2010 06:52 AM

    hendrik's Avatar

    Cool - yeah - that's possible that that was the reason.

    -hendrik

Reply to this discussion

Internal reply

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

Attaching KB article:

»

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