User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: UI becomes unresponsive and eventually crashes when pressing Add after selecting a new compilation Here's a report against 0.2.0 but I checked and it's the same for svn head. https://launchpad.net/distros/ubuntu/+source/xfburn/+bug/61579 Reproducible: Always Steps to Reproduce: 1.startx xfburn 2.select new composition 3.select add
i have seen that problem during development but i couldn't find why, i'll try to look deeper and understand what's happening
From what I can understand, the $HOME directory is the value stored in the selected_files variable, so the Add button tries to add the whole user directory if no other file have been selected after cliking the "new compisition" button.
The directory browser (left pane) is defaulted to ~/ so a default Add will add the home dir recursively which takes a lot of time or causes crashes elsewhere because of the memory usage.
(In reply to comment #3) > The directory browser (left pane) is defaulted to ~/ so a default Add will add > the home dir recursively which takes a lot of time or causes crashes elsewhere > because of the memory usage. > I'm aware of the problem i just haven't the time to fix it currently. And i don't think the problem is related to some memory usage, because if you deselect the home dir then select it again and try to add it... it works (at least i remember it worked)
> I'm aware of the problem i just haven't the time to fix it currently. And i > don't think the problem is related to some memory usage, because if you > deselect the home dir then select it again and try to add it... it works (at > least i remember it worked) I tried deselecting and then reselecting but get the same. By memory usage I mean it tries to read in thw whole ~ which may be tens of GB as in my case. When adding is done via an explicit file chooser dialog it is much less likely this can occur as users would rarely want to add their whole home-dir to the compilation.
This is still happening in Ubuntu Feisty with xfburn 0.2.0-0ubuntu2, any news on this ?
i'm still slowly working on 0.3.0, but i haven't looked into it yet.
Thank you for your bug report. Can you still reproduce the problem with svn?
I can still reproduce this with revision 4539 of trunk. I think I can try to give more details : It seems to happen for top level directories such as home, file system... and also for directories which contain only folders. If something is selected in the right column (file/size/type), it never crashes, whatever directory is selected in the left column. A solution could be to always automatically select the first item of the file/size/type column ?