audacity-2.2.2: problems with loop playback

Since some time i noticed, that loop playback is broken.

- When audacity is started using clean jack env (only alsa or dummy dev,
  without other clients, even pulseaudio or alsa_out/in), on attempt to
  play selection in loop, audacity creates jack ports, but doesn't even
connect before gui freezes, while terminal output showes more messages,
like:

Jack: JackClient::ClientNotify ref = 4 name = PortAudio notify = 3
Jack: JackClient::kXRunCallback

Loop playback without selection gives some sound, but then it still
freezes, after first loop. Or crashes with such log:

[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has
not been called [xcb] Aborting, sorry about that.
audacity: /var/calculate/tmp/portage/x11-libs/libX11-1.6.5-r1/work/libX11-1.6.5/src/xcb_io.c:165:
dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq'
failed.

If playback is stoped, while playing loop without selection, it gives
error below, then edits:

The program 'audacity' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 30387 error_code 141 request_code 138 minor_code 23)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
   function.)

Another time i managed to start loop playback without selection, then
stop - 2 times. After second time it got segmentation fault.

Next time it crashed after 1st attempt, though this time i ran it in
gdb. Backtrace lacks for debug info, but i can't rebuild audacity right
now, because right now upgrading gentoo, and just now upgraded
toolchain, while system still has to be rebuilt.
Without symbols it looks so:

Thread 13 "audacity" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcb890700 (LWP 22224)]
0x00007fffedac15cd in __memcpy_ssse3 () from /lib64/libc.so.6
(gdb) backtrace
#0  0x00007fffedac15cd in __memcpy_ssse3 () from /lib64/libc.so.6
#1  0x00007ffff74b332c in ?? () from /usr/lib64/libsoxr.so.0
#2  0x00007ffff74b0c2c in ?? () from /usr/lib64/libsoxr.so.0
#3  0x00007ffff74b267e in soxr_process () from /usr/lib64/libsoxr.so.0
#4  0x0000555555abd036 in ?? ()
#5  0x00007fffcb88f480 in ?? ()
#6  0x0000555557a42380 in ?? ()
#7  0x4014072b020c49ba in ?? ()
#8  0x40043ae147ae147b in ?? ()
#9  0x0000000000004f06 in ?? ()
#10 0xfaff15787d844a00 in ?? ()
#11 0x00007fffcb88f820 in ?? ()
#12 0x00005555582f8800 in ?? ()
#13 0x0000000000010000 in ?? ()
#14 0xfaff15787d844a00 in ?? ()
#15 0x00005555584c9400 in ?? ()
#16 0x00005555582f8800 in ?? ()
#17 0x0000000000000000 in ?? ()

In addition, it seems it saves debug reports, they are attached all in
one archive.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

*********** ASKING FOR HELP *************

When asking for help on this list, please include the following information, so we can
help you properly:

* What operating system you are using (for example, Windows XP or Mac OS X 10.5.1)

* Exactly what three digit version number of Audacity you are using (Help > About
   Audacity, or Audacity >  About Audacity on a Mac computer)

* If this is a recording problem, what equipment you are recording with, and how is it
   connected to the computer?

Mailing list: [email protected]
To UNSUBSCRIBE, use the form at the bottom of this web page:
https://lists.sourceforge.net/lists/listinfo/audacity-users