![]() ![]() ![]() Now, let's discuss how this can be solved. So, why was it using 7zip library? As far as I understand, just the fact of presence of a path within a 7-zip archive in the Recent locations (I opened a couple of 7-zip archives on the previous week) makes muCommander to try to access these 7-zip archive each time the Recent locations (Option+2) are shown! And thus muCommander crashes somewhere in 7zip library just because the Recent locations are shown! Looks like an overkill to me. OK, I've seemed to identify the root of the problem.Īccording to the crash logs, muCommander crashes somewhere in 7zip library. Actual behaviorĢ0, OpenJDK 64-Bit Server VM, 20+36. Option+2 is expected to show the Recent locations. So I don't know: maybe the crash described above was caused by the combination of different factors such as long active time and intensive usage of the Recent location together with its filtering ability and together with granting for permissions to access various folders? Or maybe (I'm just guessing), maybe there are memory leaks and another attempt to show the Recent location failed to allocate memory?Īre there some logs available (either muCommander's own log files or maybe some system log files) that could shed more light to this situation? Expected behavior At that point, muCommander crashed.Īfter muCommander has restarted, I tried to reproduce that by creating another folder under "/Users/User_Name" and then pressing Option+2 in another file panel, but everything was good, no crash. Then I pressed Tab to go the other file panel and pressed Option+2 to show the Recent locations.In the same file panel (where the "Documents" folder was opened) I went one level up (to the "User_Name" folder) and created a new folder "Tmp" there. ![]() ![]() I navigated to "/Users/User_Name/Documents", muCommander asked for permissions to access the "Documents" folder, I granted them.Right before the crash, I was going to copy a file under my "Documents" folder to a temporary folder: it was working during 4 days without being restarted) MuCommander was active since the beginning of the week (i.e. A few seconds later, Mac OS showed a message that muCommander had crashed and proposed to restart it. At some point I pressed Option+2 (Recent locations) as usual, and muCommander disappeared from the screen. MuCommander was active since the beginning of the week as was working without any issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |