Reproduced in a build without perftools. Created report
https://bugs.launchpad.net/mixxx/+bug/1885894.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789059
Title:
continual GUI freeze
To manage no
Ok I spent some time looking at the functions indicated by source files
and line numbers from other threads, like that related to CoverArtCache,
but you are right.
Have yet to test with a build without PerfTools actually. Gotta be a bit
later though.
> we should create a new issue
Will do. I was
The hang on exit while closing the sound devices is unrelated. Probably
not a deadlock, only a slow I/O operation and hardware interaction. Hard
to trace without the actual device setup at hand.
Now we know that the deadlock is originating from WOverview.
Do you still experience any deadlocks aft
Since this deadlock is probably not related to the original issue that
has already been fixed we should create a new issue. Otherwise tracking
becomes difficult.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I just had it hang when exiting the program, at a time of low CPU load.
Curiously enough, attaching the debugger in order to obtain the
backtrace was sufficient to make it recover (when I detached the
debugger the program closed successfully).
I know it sounds exotic but I'm actually documenting t
Oh, so it's related to tcmalloc. Thanks.
Here is the full backtrace with debug symbols.
** Attachment added: "backtrace - debug build"
https://bugs.launchpad.net/mixxx/+bug/1789059/+attachment/5388091/+files/2020-06-29%204H41%20gdb%20mixxx-debug.txt.html
--
You received this bug notificati
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mixxx (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789059
Title:
cont
tcmalloc could even be faster than the system allocator. But as already
mentioned this is not used in any of the official builds.
Please first do a local build with the original Arch settings and try to
reproduce the deadlock with a full stacktrace. Then rebuild without
these options.
--
You rec
https://github.com/mixxxdj/mixxx/blob/dc1b9a1e64ac48e9b926e2afd452a6651a20081d/build/features.py#L495
I have never used it myself and am unsure about the consequences or
side-effects. In the best case it results in a minor performance
regression.
Using a local build with debug infos would hopeful
Don't know. Should I build locally without it? If you can you tell me
what the implications are (or point me to some documentation or code)
I'd like to know more about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
PKGBUILD: Why is Mixxx built with "perftools=1 perftools_profiler=1"? We
don't use those options neither for CI builds nor for release builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789059
Tit
Got it, thanks.
I'm running cinnamon-4.6.5-1 with qt5-base-5.15.0-3
(https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/qt5-base).
I start Mixxx with '-platform xcb', per default, but needless since
Cinnamon runs on X (1.20.8-2). I just removed 'pasuspender' from the
official lau
Version 2.2.4 was tagged much earlier but then not released officially
due to internal build server issues. Nothing to worry about.
The issue might depend on the exact Qt version, the build settings used
by Arch, and how Mixxx is started (i.e. with "-platform xcb" on
Wayland?). I have never experi
I've been getting this on Mixxx 2.2.4 (which somehow was released to
Arch Linux much sooner than the official release which was just
yesterday) for the past 5 days or so. Maybe the fact that I'm running
JACK with tighter settings and two external USB soundcards, and
streaming with OBS studio at the
** Also affects: mixxx (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
Several times using the master branch with Qt 5.10.1 on Fedora, the GUI
has completely frozen. At first I thought it might be related to using
my touchscreen because it happened
15 matches
Mail list logo
