-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bacon crashes on rustc #10
Comments
Here's an strace in case it helps: bacon.log |
Here's
|
Maybe it's trying to write too much to the buffer? |
Bacon wasn't designed with such big project in mind. But I still don't see how the report can't fit a few times in memory. I'll have a look when I find some time (not in the next few days). |
It's crashing somewhere here by the log: Lines 47 to 62 in 0791359
|
Maybe. It's the first time I use the notify crate and to be honest I don't know it well and didn't look at the source much. |
Yup, that's definitely it - it makes it to |
Another option is to make it possible to opt-out of watching |
You mean by specifying the precise directory to watch as argument (or use the current one) ? |
@jyn514 The behavior changed with last commit (not yet released on crates.io):
This is hopefully clear in the bacon.log file. Can you tell me if it helps with the notify explosion problem and is still practicable ? |
@Canop now it gives a different error:
Here's
|
I just pushed some file existence checks |
That fixed it, thanks! |
Cool. Is it now possible and practical to use bacon with rustc, in your opinion ? |
@Canop not yet - |
It runs
cargo check
, finishes seeing all the 'duplicate lang error's, then immediately exits withdf -h
reports 300 GB free, so I don't expect that to be the issue.The text was updated successfully, but these errors were encountered: