Bug 135234 - Crashes if the disk housing the temporary directory fills up.
Summary: Crashes if the disk housing the temporary directory fills up.
Status: RESOLVED FIXED
Alias: None
Product: kaudiocreator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Gerd Fleischer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-07 02:43 UTC by Chris Roe
Modified: 2010-08-29 09:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Roe 2006-10-07 02:43:24 UTC
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 Richard Lärkäng 2006-11-08 17:31:16 UTC
Did you get a backtrace, or did the window just disappear?

I couldn't reproduce the bug with either 3.5.2 or from a recent 3.5 branch, all I got was a message box saying the disk was full.
Comment 2 Chris Roe 2006-11-09 00:52:12 UTC
No backtrace as far as I could tell, the window just disappeared.  I am going to be re-building my linux box tonight.  If you want, I'll try it again in a day or two, just let me know.

Since I am using Gentoo, perhaps it is a bug in their ebuild (the thing that tells the package how to compile).  Although, I filed a bug with them first and they sent me here (rather quickly IMHO).
Comment 3 Richard Lärkäng 2006-11-14 15:53:26 UTC
If it just disappears, it would be good if you could run it from a terminal, and see if there are at least any error messages written out.