{"action":"created","issue":{"url":"https://api.github.com/repos/hasse69/rar2fs/issues/64","repository_url":"https://api.github.com/repos/hasse69/rar2fs","labels_url":"https://api.github.com/repos/hasse69/rar2fs/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/hasse69/rar2fs/issues/64/comments","events_url":"https://api.github.com/repos/hasse69/rar2fs/issues/64/events","html_url":"https://github.com/hasse69/rar2fs/issues/64","id":202219787,"number":64,"title":"FreeBSD: Memory usage and mtime","user":{"login":"zappepappe","id":25253093,"avatar_url":"https://avatars.githubusercontent.com/u/25253093?v=3","gravatar_id":"","url":"https://api.github.com/users/zappepappe","html_url":"https://github.com/zappepappe","followers_url":"https://api.github.com/users/zappepappe/followers","following_url":"https://api.github.com/users/zappepappe/following{/other_user}","gists_url":"https://api.github.com/users/zappepappe/gists{/gist_id}","starred_url":"https://api.github.com/users/zappepappe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zappepappe/subscriptions","organizations_url":"https://api.github.com/users/zappepappe/orgs","repos_url":"https://api.github.com/users/zappepappe/repos","events_url":"https://api.github.com/users/zappepappe/events{/privacy}","received_events_url":"https://api.github.com/users/zappepappe/received_events","type":"User","site_admin":false},"labels":[{"id":186601739,"url":"https://api.github.com/repos/hasse69/rar2fs/labels/Defect","name":"Defect","color":"e11d21","default":false},{"id":320888160,"url":"https://api.github.com/repos/hasse69/rar2fs/labels/Priority-High","name":"Priority-High","color":"bfd4f2","default":false}],"state":"open","locked":false,"assignee":{"login":"hasse69","id":1021198,"avatar_url":"https://avatars.githubusercontent.com/u/1021198?v=3","gravatar_id":"","url":"https://api.github.com/users/hasse69","html_url":"https://github.com/hasse69","followers_url":"https://api.github.com/users/hasse69/followers","following_url":"https://api.github.com/users/hasse69/following{/other_user}","gists_url":"https://api.github.com/users/hasse69/gists{/gist_id}","starred_url":"https://api.github.com/users/hasse69/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hasse69/subscriptions","organizations_url":"https://api.github.com/users/hasse69/orgs","repos_url":"https://api.github.com/users/hasse69/repos","events_url":"https://api.github.com/users/hasse69/events{/privacy}","received_events_url":"https://api.github.com/users/hasse69/received_events","type":"User","site_admin":false},"assignees":[{"login":"hasse69","id":1021198,"avatar_url":"https://avatars.githubusercontent.com/u/1021198?v=3","gravatar_id":"","url":"https://api.github.com/users/hasse69","html_url":"https://github.com/hasse69","followers_url":"https://api.github.com/users/hasse69/followers","following_url":"https://api.github.com/users/hasse69/following{/other_user}","gists_url":"https://api.github.com/users/hasse69/gists{/gist_id}","starred_url":"https://api.github.com/users/hasse69/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hasse69/subscriptions","organizations_url":"https://api.github.com/users/hasse69/orgs","repos_url":"https://api.github.com/users/hasse69/repos","events_url":"https://api.github.com/users/hasse69/events{/privacy}","received_events_url":"https://api.github.com/users/hasse69/received_events","type":"User","site_admin":false}],"milestone":null,"comments":202,"created_at":"2017-01-20T19:18:08Z","updated_at":"2017-02-01T12:19:45Z","closed_at":null,"body":"Hello!\r\n\r\nI have a pretty large rar archive that I need to scan from time to time for changes.\r\nEvery time I do rar2fs will eat up all the RAM it can get its hands on and eventually, (anything from hours to weeks) depending on how much I use the files in the mount, rar2fs will crash. Taking a long time to shut itself down almost making the computer unusable in the meantime.\r\n\r\nI have been working around this problem by doing the scan, then unmounting and remounting rar2fs.\r\nThe application making the scans does have the feature to check for new files automatically, but I believe it uses mtime to see what's new. So a feature like -relatime but for mtime would probably help a lot and limit the amount of scans needed.\r\n\r\nMount options: rar2fs --seek-length=1 --iob-size=1 --hist-size=0 -o allow_other\r\n\r\nrar2fs v1.23.1 (DLL version 7)    Copyright (C) 2009 Hans Beckerus\r\nFUSE library version: 2.9.5\r\nmount_fusefs [fuse4bsd] version: 0.3.9-pre1\r\nusing FUSE kernel interface version 7.19\r\n\r\nFreeNAS 9.10 (FreeBSD 10.3)"},"comment":{"url":"https://api.github.com/repos/hasse69/rar2fs/issues/comments/276644085","html_url":"https://github.com/hasse69/rar2fs/issues/64#issuecomment-276644085","issue_url":"https://api.github.com/repos/hasse69/rar2fs/issues/64","id":276644085,"user":{"login":"hasse69","id":1021198,"avatar_url":"https://avatars.githubusercontent.com/u/1021198?v=3","gravatar_id":"","url":"https://api.github.com/users/hasse69","html_url":"https://github.com/hasse69","followers_url":"https://api.github.com/users/hasse69/followers","following_url":"https://api.github.com/users/hasse69/following{/other_user}","gists_url":"https://api.github.com/users/hasse69/gists{/gist_id}","starred_url":"https://api.github.com/users/hasse69/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hasse69/subscriptions","organizations_url":"https://api.github.com/users/hasse69/orgs","repos_url":"https://api.github.com/users/hasse69/repos","events_url":"https://api.github.com/users/hasse69/events{/privacy}","received_events_url":"https://api.github.com/users/hasse69/received_events","type":"User","site_admin":false},"created_at":"2017-02-01T12:19:45Z","updated_at":"2017-02-01T12:19:45Z","body":"Thanks. I am starting to get a small hint about what is going on here. It seems to me that it is the thread library that crashes when one of the threads created by rar2fs implicitly calls pthread_exit. I know I removed all direct calls to pthread_exit in the code because I found out that the C++ exception handler sometimes caused the application to crash. This might be something in the C++ run-time environment that is behaving strange, maybe in combination with low memory? \n\nWhat we can try here is to kill the thread with a bit more brute force. Maybe that will workaround this issue. Should not really matter as long as the thread dies. It does not allocate any resources on its own so there is no risk of leaks that I can think of. It might also be that I am wrong here of course.\n"}}
{"actor":{"display_login":"hasse69"}}