Bug 249390 - Crashes if the disk housing the temporary directory fills up.
Summary: Crashes if the disk housing the temporary directory fills up.
Status: RESOLVED WORKSFORME
Alias: None
Product: kaudiocreator
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Gerd Fleischer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 09:54 UTC by Gerd Fleischer
Modified: 2023-01-17 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Fleischer 2010-08-29 09:54:07 UTC
+++ This bug was initially created as a clone of Bug #135234 +++

Version:           1.13 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9) Thread Model: Posix
OS:                Linux

This bug sounds very similar to 94641, however, I am not getting a dialog box, KAudioCreator just disappears.

When ripping CDs and the ripping process gets too far ahead of the encoding
process, The temporary directory fills with *.wav files that are waiting to be
encoded.  I have the temporary directory on its own partition (a logical volume
actually), and when this disk fills, KAudioCreator does not handle the
situation, but rather disappears and stops all encoding that goes on.

Steps to Reproduce:
1. Create a small partition or logical volume (Mine is 1GB) and mount it
2. Set your temporary directory in KAudioCreator to this mount point.
3. Set the number of encoders to 1.  Choose an encoding option that takes a bit
of processing power and is generally slower than the rip of the same song (I
used ogg)
4. Set the number of ripping processes higher than 1 if you can (optional).
5. Start ripping CDs.  Once a CD has been ripped, pop in another right away
(don't wait for the encoding to be done).  Keep doing this until you temporary
area fills up and KAudioCreator crashes.

Actual Results:  
KAudioCreator crashed.

Expected Results:  
If it is the temp location that is out of space and there are encoding jobs
still to be done (and the target of the encoding jobs is a different volume
than
the temp dir), pause the ripping until space becomes available (i.e. encoding
catches up and removes some wave files).

If the temp dir fills up and it is on the same volume as the target directory,
pause everything and display an error to the user, giving them a chance to
rectify the issue and continue where they left off.

If the target directry fills, pause all encoding and display an error to the
user giving them a chance to rectify the issue and continue where they left
off.
Comment 1 Gerd Fleischer 2010-08-29 09:55:39 UTC
Cloned the bug as with normal severity as it doesnt crash anymore but maybe we can do something for the expected results.
Comment 2 Andrew Crouthamel 2018-11-05 03:13:26 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-17 05:03:43 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-18 08:18:31 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-02 05:26:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-17 05:17:52 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!