> This is probably related to threading issues and timing-specific. > is not called, but when it is (it is random), then it crashes. > working directory - both file_a- >collate_ key_nocase and > thunar_ file_compare_ by_name( ) function is called even for only one file in > gdb backtrace attached - it is strange that the > check-thunar- file-instance- when-comparing- filenames. (In reply to Harald Judt from comment #1) UpgradeStatus: Upgraded to wily on (156 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) InstallationDate: Installed on (268 days ago) =28859= ERROR SUMMARY: 1046 errors from 45 contexts (suppressed: 0 from 0) =28859= Use -track-origins=yes to see where uninitialised values come from =28859= For counts of detected and suppressed errors, rerun with: -v =28859= The main thread stack size used in this run was 8388608. =28859= main thread stack using the -main-stacksize= flag. =28859= possible), you can try to increase the size of the =28859= overflow in your program's main thread (unlikely but =28859= If you believe this happened as a result of a stack =28859= Access not within mapped region at address 0x0 =28859= Process terminating with default action of signal 11 (SIGSEGV) =28859= Address 0x0 is not stack'd, malloc'd or (recently) free'd =28859= at 0x04c2ffd3: strcmp (in /usr/lib/ valgrind/ vgpreload_ memcheck- amd64-linux. Running thunar in valgrind produces these log entries in the moment of the crash: When renaming files in a folder while re-sorting similarly named files, thunar crashes fairly often. Testing this bug and potentially instigating a crash. * Since Thunar is a file manager, there is a risk of data loss when * However, with the frequency that this bug crashes Thunar with theĮxisting package, any reduction in the number of crashes are welcome. * The patches have not been tested in all possible configurations,Īnd could result in unexpected behavior (possibly additional crashing). Thunar to crash on the first rename or after several. * Backup the file you will be testing to a different location. Was originally reported, and numerous users are now reporting that
* There have been several patches addressing this issue since the bug
#GTASKS PRO CRASHES WINDOWS#
* All open Thunar windows are closed, disrupting a user's workflow. * Thunar crashes frequently when renaming files.
0 kommentar(er)
