Nightly Distribution of the master branch

Build: #1864 was successful Changes by Florian Schmaus <>

Stages & jobs

  1. Default Stage

  2. Deploy

Build result summary


Queue duration
< 1 second
13 minutes
70d0843dd8c8f45304eaa3dc03b136dc9095074d 70d0843dd8c8f45304eaa3dc03b136dc9095074d
Total tests
First to pass since
#1860 (Changes by Ingo Bauersachs <> and Florian Schmaus <>)


Code commits

Author Commit Message Commit date
Florian Schmaus <> Florian Schmaus <> 70d0843dd8c8f45304eaa3dc03b136dc9095074d 70d0843dd8c8f45304eaa3dc03b136dc9095074d Merge branch '4.4'
Florian Schmaus <> Florian Schmaus <> c9af6576c07fa94f6f6be22d8f5a50a7ebf9a426 m c9af6576c07fa94f6f6be22d8f5a50a7ebf9a426 Merge pull request #529 from Flowdalic/fix-sd-memleak
[disco] Fix memory leak in ServiceDiscoveryManager
Florian Schmaus <> Florian Schmaus <> 69e81b748ed95a1b4422c44141a39968691475d9 m 69e81b748ed95a1b4422c44141a39968691475d9 [disco] Only perform entity capabilities work if there are any listeners
Florian Schmaus <> Florian Schmaus <> 5b6dd8e3f77a1e2deec0b4be32ca34759a7027cf m 5b6dd8e3f77a1e2deec0b4be32ca34759a7027cf [disco] Fix memory leak in ServiceDiscoveryManager
The lambda we schedule in 25ms captures a strong reference to the
XMPPConnection. However the lambda is part of the scheduled action,
which we save in the renewEntityCapsScheduledAction field. This causes
a memory leak, since the ServiceDiscoveryManager now holds a strong
reference to its XMPPConnection.

Fix this by obtaining the strong reference to the XMPPConnection, if
one still exists, within the lambda.

Fixes SMACK-926.

Reported-by: Damian Minkov <>

Jira issues

Unknown Issue TypeSMACK-926Could not obtain issue details from Jira