Conversation

Notices

1. a1ba-nyan (a1ba@expired.mentality.rip)'s status on Sunday, 06-Mar-2022 03:55:01 UTC a1ba-nyan
   file-roller vs ark absolutely subjective benchmark on 50GB 7z archive
   
   file-roller: *fast but segfaults*
   ark: *slow but stable*
   • niconiconi (niconiconi@cybre.space)'s status on Sunday, 06-Mar-2022 03:55:00 UTC niconiconi

     in reply to

     @a1ba if someone wants to report a bug, sending that 50 GB 7z file reproducer to the developer would be an "interesting" exercise. I still remember uploading my 16 GB disk image to AWS for reportitng a F2FS bug, I was impressed by hom much patience the developers had on me... :blobcatgiggle:

     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • friend@linuxrocks.online's status on Sunday, 06-Mar-2022 03:55:46 UTC friend

     in reply to

     • niconiconi

     @niconiconi
     Well, those kind of bugs are a bitch to track down, so getting sample data which reliably reproduces it, is incredibly helpful.
     @a1ba

   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Sunday, 06-Mar-2022 03:55:46 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • niconiconi
     • friend
     @friend @a1ba @niconiconi Scripts to reproduce a huge problematic archive might be possible.
   • friend@linuxrocks.online's status on Sunday, 06-Mar-2022 09:57:45 UTC friend

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     • niconiconi

     @clacke
     Sure, but to write such a script, you need a pretty solid suspicion of what's causing the problem. If you can inspect an existing archive, thats a lot easier.
     @niconiconi

     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Sunday, 06-Mar-2022 09:58:51 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • niconiconi
     • friend
     @friend @niconiconi True; Depends on how much insight is required to reproduce the issue.