QObject::startTimer: error
Bug #197328 reported by
Albert Santoni
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Critical
|
Adam Davison | ||
Bug Description
From the old bug tracker:
=============
when trying to drag a track from my library onto either of the channel's (1
or 2) an immediate pop up window comes up and says
QObject:
my only option is to hit OK
it then proceeds to open up numerous instances of thie same error message.
clicking OK is futile because 40 or so of the same windows have already
opened up and covered my desktop.
after waiting a few seconds, I roll over the OK button and Mixxx shuts down
and I am back at my empty desktop.
=============
| Changed in mixxx: | |
| assignee: | nobody → adamdavison |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
Revision history for this message
| Albert Santoni (gamegod) wrote | #1 |
Revision history for this message
| Albert Santoni (gamegod) wrote | #2 |
| Changed in mixxx: | |
| status: | Confirmed → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #4 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
Extra information from Adam and I's discussion:
We've had this happen to us when some other error message pops up first, then the barrage of QTimer messages happen. Might be a weird race condition where some thread gets blocked by the first error message, causing another thread to go bonkers.