Possible memory leak in developer mode

Bug #1757408 reported by Peter Burg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
New
Low
Unassigned

Bug Description

Assigned memory is growing from 1.5 GB till 4.5 GB in 24 Hours playing AutoDJ. (developer mode)
All tracks are already assigned with all additional data like waveforms beat-detection and pitch. Checked on Deere and Tango interface
Win7-64 AMD4core 8GB
2.1 beta 6528

Peter Burg (wunjo)
description: updated
Peter Burg (wunjo)
description: updated
Changed in mixxx:
importance: Undecided → Critical
milestone: none → 2.1.0
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Please retest with developer mode disabled. I wouldn't rate this as critical if it only happens when developer mode is enabled.

Revision history for this message
Peter Burg (wunjo) wrote :

I'm sorry, I broadcast at A=432Hz, witch is only (nearclose) possible in developer mode. (pitch_adjust -0,32)

Revision history for this message
Peter Burg (wunjo) wrote :

I really appreciate the work you're doing, it is a great tool! Thanks!

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I cannot reproduce this on win10 with the latest beta 64 bit

Be (be.ing)
Changed in mixxx:
importance: Critical → Low
milestone: 2.1.0 → none
summary: - Possible memory leak stll in Windows7
+ Possible memory leak in developer mode
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/9182

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.