Crash-m / thelastripper

Automatically exported from code.google.com/p/thelastripper
0 stars 0 forks source link

out of disk space #54

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Description of the issue:
thelastripper encouters problems when you run out of disk space.

What steps will reproduce the problem?
1. be low on disk space
2. run last ripper & rip songs
3. run out of disk space
4. lastripper continues to show it is ripping songs with any notification
of disk space issue
5. songs do not get sent to files because no space but there is no
notification of this and it continues to seem to rip songs
6. open preferences...
7. close preferences...
8. crashes... prints error message to kernal (similar if not the same as
one below)
9. run program again with no free disk space
10 fails to launch, gives error:

** (/usr/local/lib/thelastripper/TheLastRipper.exe:6556): CRITICAL **:
_wapi_shm
_file_open: shared file
[/home/timmy/.wapi/shared_data-tim-lin-deb-Linux-i686-31
2-11-0] write error: No space left on device

** (/usr/local/lib/thelastripper/TheLastRipper.exe:6556): CRITICAL **:
_wapi_shm
_attach: shared file
[/home/timmy/.wapi/shared_data-tim-lin-deb-Linux-i686-312-1
1-0] open error

** ERROR **: file shared.c: line 312 (_wapi_shm_semaphores_init): assertion
fail
ed: (tmp_shared != NULL)
aborting...
Stacktrace:

Native stacktrace:

        mono [0x8179af1]
        mono [0x815c692]
        [0xb7ef7440]
        /lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xb7d00fb9]
        /usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xb7e7c074]
        /usr/lib/libglib-2.0.so.0(g_log+0x29) [0xb7e7c0a9]
        /usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xb7e7c127]
        mono [0x811ea78]
        mono [0x811a8a9]
        mono(mono_once+0x91) [0x811f165]
        mono [0x811ae74]
        mono [0x81157b0]
        mono [0x8115e2c]
        mono [0x810084e]
        mono(mono_runtime_init+0x1a) [0x80f33b2]
        mono [0x815d8aa]
        mono(mono_main+0x130d) [0x8059e46]
        mono [0x8057ab6]
        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7cebea8]
        mono [0x8057a11]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211279680 (LWP 6556)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7ef7410 in ?? ()
  1 Thread -1211279680 (LWP 6556)  0xb7ef7410 in ?? ()

Thread 1 (Thread -1211279680 (LWP 6556)):
#0  0xb7ef7410 in ?? ()
#1  0xbfd8ab1c in ?? ()
#2  0x00000000 in ?? ()
#0  0xb7ef7410 in ?? ()

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted
timmy@tim-lin-deb:~$

What would be really good would be a function which checks desination disk
space situation on launch and immediatly after writing mp3's to disk.
Obviously, whether you regard this as a feature request or bug report isn't
obvious.

obviously it works best when you have disk space for stuff, but crasing
without a graphical notification is probably not the best way to
communicate this to the user.

GENERAL INFORMATION ABOUT YOUR SYSTEM:

TheLastRipper version? 1.1 debian stable
Mono/.Net runtime version? not sure... probably a version or two of mono
behind the current version
Operating system and version? debian stable (4GB HardDrive)

Original issue reported on code.google.com by timmydob...@gmail.com on 20 Aug 2007 at 10:36

GoogleCodeExporter commented 9 years ago
Well, this is a little unusual case :)

I think it would be overkill to check for diskspace, but a dialog for handling
exceptions is probably a good idea... I've made such a dialog on windows, 
showing
users the exception and telling them to open an issue... etc..
But I was kind of hoping that it would be possible to interact with some system 
crash
handler under Linux... It looks better and gives me less to maintain...
I currently know that Ubuntu has https://wiki.ubuntu.com/Apport, but I'm not 
sure if
TheLastRipper should interface it...

Original comment by jopsen@gmail.com on 20 Aug 2007 at 2:51

GoogleCodeExporter commented 9 years ago
um, are you sure you think its overkill to check disk space...?
i mean what i found disconcerting was that i didnt know - i just thought it 
wasn't
working - especially considering i have compiled it etc.

Yeah i realise it is unusual. The crash handlers i have encounteres aren't very
usefulll... the best i can think of is amaroks which attempts to use kmail to 
send
bug report/backtrace to mailing list....

what about having the option to be notified or to have it stop ripping when the 
disk
is full... If i could write c# 

i dunno what i suggest really... people might use last ripper onto usb
sticks/memorycards....

Original comment by timmydob...@gmail.com on 21 Aug 2007 at 1:07

GoogleCodeExporter commented 9 years ago
As you suggest some people may be writing directly to USB sticks or mp3-players,
where storage might be limited... It's seams like a good reason to check 
available
disk space . Considering that the main purpose to use TheLastRipper usually 
would be
to take Last.fm onto our mp3-player...

I think this is a bug that will be fixed in next minor release, unless next 
release
is a major :)

Original comment by jopsen@gmail.com on 21 Aug 2007 at 2:51

GoogleCodeExporter commented 9 years ago
if you want me to test any disk space routines im living on a v small HD at the
moment so its very easy.... :)
I had the idea for a few features a while back but i have forgotten them now... 
i'll
let you know when i remember...

Original comment by timmydob...@gmail.com on 31 Aug 2007 at 10:31