FS#63201 - [deluge] std::bad_alloc
Attached to Project:
Arch Linux
Opened by John Martelle (johnmartelle) - Monday, 15 July 2019, 12:34 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 21:33 GMT
Opened by John Martelle (johnmartelle) - Monday, 15 July 2019, 12:34 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 21:33 GMT
|
Details
Description: When starting deluge, it terminates with the
following error "terminate called after throwing an instance
of 'std::bad_alloc'
what(): std::bad_alloc" Additional info: * package version(s) = 2.0.3-1 * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: Launch deluge from terminal. |
This task depends upon
Closed by freswa (frederik)
Saturday, 22 February 2020, 21:33 GMT
Reason for closing: None
Additional comments about closing: This seems pretty stalled to me. If it's still an issue, please fill a re-open request. Thank you :)
Saturday, 22 February 2020, 21:33 GMT
Reason for closing: None
Additional comments about closing: This seems pretty stalled to me. If it's still an issue, please fill a re-open request. Thank you :)
I am unable to reproduce, the issue. A std::bad_alloc error is related to memory allocation. Do you have enough memory available when starting deluge? Do you have any big torrents or something running inside the application which might take up a lot of memory?
Could you please provide your configuration, a log file if available and a stack trace for further investigation?
I have big torrents placed in an external partition. When starting Deluge comes a system warning that the root partition space is empty. I think that this version of Deluge cannot remember the right path. I downgraded it and now it works well.