Skip to content
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

[request] print informative error if fwrite uses more memory than allowed #2612

Closed
zachokeeffe opened this issue Feb 7, 2018 · 1 comment · Fixed by #3288
Closed

[request] print informative error if fwrite uses more memory than allowed #2612

zachokeeffe opened this issue Feb 7, 2018 · 1 comment · Fixed by #3288
Milestone

Comments

@zachokeeffe
Copy link

@zachokeeffe zachokeeffe commented Feb 7, 2018

This request follows my post on StackOverflow. I've found that fwrite will do strange things in memory constrained environments. If write.table uses more memory than it is allowed, I've found that my high performance computing cluster will kill the job. But if I use fwrite, the job will not be killed--instead, fwrite will either write nothing, write an empty file, write part of the file, or write the file with errors--but the R code will appear to have finished correctly. It's taken me quite some time to figure this all out--it would be nice if there were a way to alert users in the future that the write operation failed because of memory constraints (i.e., so they know they just need to boost the RAM allocation instead of hunting down errors in their code that don't exist). I don't imagine that's an easy task (I know this is a rather vague request), but I thought I would bring this to your attention because I've spent the last few days wrangling with the issue.

@mattdowle
Copy link
Member

@mattdowle mattdowle commented Apr 23, 2019

Thanks for this report. I'm confident that PR #3288 by @philippechataignon with some follow up from me, should solve this. When that PR is merged, it will close this issue. Please reopen if it comes up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants