Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1670 closed Discussion (fixed)

Jajuk constantly reading from hard drive

Reported by: mats.ahlgren@… Owned by:
Priority: 1, lowest Milestone: To Be Qualified by Jajuk Team
Component: Core Version: 1.9RC4
Keywords: Cc:
Regression ?:


Jajuk is constantly reading from my hard drive

Of course, this normally is fine and expected. The issue is that the reads are so large and so frequent and so unnecessary that it is (unfortunately) abusing the hard drive bandwidth. I'm clocking about 4-10MB (bytes) per second all the time. It's like it's trying to read my entire mp3 collection into memory. I know Jajuk is trying to read tag information since I've seen the ~/.jajuk/jajuk.log file being appended to as I was looking at it; but Jajuk already has all the tag information in the database.

It's going through about 1GB every 2min. At this rate, my hard drive will die much more quickly.

All reading stops when I kill Jajuk, and starts again very soon after I restart it (<1min).

Please note that I recently upgraded to RC4; though it bears mentioning that I think previous versions of Jajuk had this issue as well, but I did not notice it.

By comparison, a "find ." will dump my all the paths in the collection within 20sec. And tags only need to be read from new (or possibly changed) files.

Suggested severity: Severe


Linux, OpenSuse? 10.3, Java 1.6.0_18

(sidenote: KDE4 + Compiz)

Attachments (0)

Change History (3)

comment:1 Changed 4 years ago by mats.ahlgren@…

Sorry, seems like this may have been just a very long Deep Refresh.

Tag data is only read for new files, correct? If so, the reading of tag data can probably be blamed on bug #1630. If not, this is also probably a bug.

comment:2 Changed 4 years ago by bflorat

  • Component changed from (Jajuk Members) Any (Default Component) to (Java Developer) Core
  • Resolution set to fixed
  • Status changed from new to closed

You guessed it, jajuk needs to read audio tags either for new discovered files or during a forced deep refresh.

As a matter of fact, if files are seen as new but shouldn't (bug, #1630), this bug may indeed emerge. Note that as a workaround, you can set the fast refresh interval to a longer period (go to device view -> double click on a device -> set refresh interval).

BTW, AFAIK all studies I read concluded that using intensively an hard disk doesn't alter its life time.

comment:3 Changed 4 years ago by mats.ahlgren@…

Thank you for providing a workaround! =)

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.