Bug 2170736 - Transmission 4.00 crashes
Summary: Transmission 4.00 crashes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: transmission
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-17 06:35 UTC by Stephen So
Modified: 2023-03-11 03:08 UTC (History)
7 users (show)

Fixed In Version: transmission-4.0.1-1.fc37 transmission-4.0.1-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-26 03:36:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stephen So 2023-02-17 06:35:43 UTC
Description of problem:

After upgrading to the new Transmission 4.00, I've been getting a lot of crashes during operation.  Starting it in the terminal, every time it crashes, it prints the following error message.

assertion failed: loc.block_offset + n_this_pass <= block_size (/builddir/build/BUILD/transmission-4.0.0/libtransmission/peer-msgs.cc:1446)

Version-Release number of selected component (if applicable):

transmission-gtk-4.0.0-2.fc37.x86_64

How reproducible:

always

Steps to Reproduce:
1.  Start transmission BT 4.00
2.  Download a torrent
3.  Wait while downloading

Actual results:

Transmission crashes and error message appears in terminal (assertion failed: loc.block_offset + n_this_pass <= block_size (/builddir/build/BUILD/transmission-4.0.0/libtransmission/peer-msgs.cc:1446)

Expected results:

It should run with no crashes (version 3 ran perfectly fine before)

Additional info:

Comment 1 bengt 2023-02-20 13:48:37 UTC
transmission-4.0.0-2.fc37 - failed with core-dump after running for a while. transmission-4.0.0-3.fc37 failed after only a few minutes. It can be random when it crash. A few lines from log transmission-4.0.0-2.fc37:

Feb 16 11:34:34 hostname transmission-daemon[770]: [2023-02-16 11:34:34.139] ERR utils.cc:72 Couldn't read '/var/lib/transmission/.config/transmission-daemon/resume/81e0b8c596dfe5d1ce7fdd32f0e5847328c44de1.resume': No such file or directory (2) (/builddir/build/BUILD/transmission-4.0.0/libtransmission/utils.cc:72)
Feb 16 11:34:36 hostname transmission-daemon[770]: [2023-02-16 11:34:36.139] ERR utils.cc:72 Couldn't read '/var/lib/transmission/.config/transmission-daemon/resume/f5380a5fdd4cfef41ceb70f655b5d05f47bd8c87.resume': No such file or directory (2) (/builddir/build/BUILD/transmission-4.0.0/libtransmission/utils.cc:72)
Feb 16 12:06:02 hostname transmission-daemon[770]: /usr/include/c++/12/bits/stl_algo.h:3623: constexpr const _Tp& std::clamp(const _Tp&, const _Tp&, const _Tp&) [with _Tp = long unsigned int]: Assertion '!(__hi < __lo)' failed.
Feb 16 12:06:03 hostname systemd[1]: transmission-daemon.service: Main process exited, code=dumped, status=6/ABRT
Feb 16 12:06:03 hostname systemd[1]: transmission-daemon.service: Failed with result 'core-dump'.

and transmission-4.0.0-3.fc37 - stop immediatly:

Feb 16 13:59:26 hostname systemd[1]: Starting transmission-daemon.service - Transmission BitTorrent Daemon...
Feb 16 13:59:26 transmission.fredhs.net systemd[1]: Started transmission-daemon.service - Transmission BitTorrent Daemon.
Feb 16 13:59:27 hostname transmission-daemon[751]: [2023-02-16 13:59:27.805] ERR watchdir-inotify.cc:90 Couldn't watch '/data/download/blackhole': No such file or directory (2) (/builddir/build/BUILD/transmission-4.0.0/libtransmission/watchdir-inotify.cc:90)
Feb 16 14:05:37 hostname transmission-daemon[751]: /usr/include/c++/12/bits/stl_algo.h:3623: constexpr const _Tp& std::clamp(const _Tp&, const _Tp&, const _Tp&) [with _Tp = long unsigned int]: Assertion '!(__hi < __lo)' failed.
Feb 16 14:05:38 hostnamesystemd[1]: transmission-daemon.service: Main process exited, code=dumped, status=6/ABRT
Feb 16 14:05:38 hostname systemd[1]: transmission-daemon.service: Failed with result 'core-dump'.
Feb 16 14:05:38 hostname systemd[1]: transmission-daemon.service: Consumed 15.947s CPU time.

Comment 2 Gwyn Ciesla 2023-02-23 16:12:41 UTC

*** This bug has been marked as a duplicate of bug 2169837 ***

Comment 3 Fedora Update System 2023-02-23 16:43:43 UTC
FEDORA-2023-d871cda59a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d871cda59a

Comment 4 Fedora Update System 2023-02-24 03:38:41 UTC
FEDORA-2023-d871cda59a has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d871cda59a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d871cda59a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-02-25 05:05:44 UTC
FEDORA-2023-75c113bcf7 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-75c113bcf7

Comment 6 Fedora Update System 2023-02-26 02:01:42 UTC
FEDORA-2023-75c113bcf7 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-75c113bcf7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-02-26 03:36:15 UTC
FEDORA-2023-d871cda59a has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-03-11 03:08:54 UTC
FEDORA-2023-75c113bcf7 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.