https://bugs.kde.org/show_bug.cgi?id=526989
Bug ID: 526989
Summary: Stack overflow exception on
ConnectionMultiplexer::bytesWritten
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: windows-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
Upon attempting to refresh multiple times in the Windows desktop client, after
a few seconds kdeconnectd will crash due to a stack overflow exception, caused
by a recursive call on line 322 in connectionmultiplexer.cpp, `auto num_written
= mSocket->write(to_write_bytes);`.
STEPS TO REPRODUCE
1. Compiled kdeconnect from Craft to access debug symbols
2. Opened the program. There are no prior device connections. Attach Visual
Studio to kdeconnectd for debugging.
3. Opened settings to enable Bluetooth
4. Clicked the refresh button multiple times (as there's no visual feedback
when it's clicked, I try clicking it multiple times to make sure it's working)
5. Wait a few seconds
OBSERVED RESULT
kdeconnectd throws a stack overflow exception, triggered by the line mentioned
above. kdeconnectd exits, with no indication from the GUI that the backend had
crashed. Clicking refresh restarts kdeconnectd.
EXPECTED RESULT
Program should not crash, and ideally show any bluetooth devices running kde
connect. Perhaps the refresh button should be disabled while it's refreshing,
in order to prevent it from being clicked improperly and causing the crash.
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Windows 11 25H2
KDE Plasma Version: N/A
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
There are issues with my computer in seeing my phone at all, let alone over
bluetooth, which this bug may be dependent on, but as far as I know it's
reproducible on my end from performing the steps described above.
--
You are receiving this mail because:
You are watching all bug changes.
