Huge Log files

Bug #1467724 reported by na
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Won't Fix
Medium
Unassigned

Bug Description

I added about 10,000 songs to my library in mixxx. And then I started systematically going through one of my big folders and adding songs to a new crate via the Browse section. After that, I started rating songs in the crate. At some point I noticed that some of the ratings I had inputted were being deleted (zeroed out), which was frustrating. (I think I resarted Mixxx once and had to kill it- but that didn't help the ratings stay). I ended up finishing what I was working on and left it open.

I then started to test out audio players (Banshee, Rhythmbox...)...this part probably isn't relevant. Anyways, stuff was getting weird and crashing (could be independent of mixxx). But I ended up discovering two HUGE mixxx logs in ~/.mixxx. They were each like 5 gigs each, and I had maxed out my partition because of it.

I don't know how much this helps.

Here are my specs:
-Computer-
Processor : 4x Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Memory : 7872MB
Operating System : Debian GNU/Linux 8.1
-Display-
Resolution : 1920x1080 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : USB-Audio - SAMSON Graphite M32
Audio Adapter : USB-Audio - Scarlett 2i2 USB
 Video Bus

I'm using the 1.12.0-beta1 (build 1.12 r5442)

Tags: logs
na (formirthonly)
description: updated
Changed in mixxx:
milestone: none → 1.12.0
importance: Undecided → Critical
Revision history for this message
Daniel Schürmann (daschuer) wrote :

I assume the log files are trashed now.
Did you had a look to it? Was there a message that was repeated over and over again?

You may start Mixxx from a terminal and watch the log. Can you identify any Mixxx action that is too verbose?
Are you able to re trigger the spamming?

To avoid massing around with your database you may create a second one by staring Mixxx with an alternate settings path
mixxx --settingsPath ~/.mixxx2

Revision history for this message
na (formirthonly) wrote :

Hi - yes, they are gone. unfortunately I wasn't thinking about whether to report it until I after I deleted the files.

I played around with mixxx again today, trying to replicate what happened, but I couldn't get the spamming. I even imported my whole library into Banshee again, and mixxx read that library perfectly fine. I watched the logging as it ran and didn't see anything crazy. ~/.mixxx2 came out to under 30mb after a few sessions.

I keep an eye on it though.

Revision history for this message
Owen Williams (ywwg) wrote :

marking incomplete and not critical

Changed in mixxx:
status: New → Incomplete
importance: Critical → Medium
Revision history for this message
Daniel Schürmann (daschuer) wrote :

The logging has been changed since the original report. So this does not apply any more.

Changed in mixxx:
status: Incomplete → Won't Fix
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8124

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.