Just wondering, what is that file for. Seems it did not break Galaxy installation for deleting it, but it would be nice to know what it is (google did not help much). Yes, made an issue report from it.. this was kinda of facepalming hilarious.. Record? :-D

Twohundredthirty gigabytes?! :-O Something is running amok.

And no, no clue what the file is.

I also have no clue what happened to your file, but my cef.log file is 784kb and contains a log about what I think should be failed commands (mutually background issues, as I never experienced any notable crashes etc.)

CEF is this.
The log file ... Delete it.

I guess Windows also needs something like logrotate.

https://sourceforge.net/projects/logrotatewin/

Or if the log file really is meh, can it be disabled?

Thx, this answered to my question, what it is :) Yup. deleted it. It was a bit hilarious, when started to check what takes room in c-drive :-D

Sometimes it is worth it to check though, why exactly the log file is growing. Since for other people that log file seems to be quite small, it seems in your system something behaves differently that the logger feels it needs to log all those constant anomalies.

For instance, at work I was once supposed to check why a client's small server was running out of hard drive space. Turns out one certain log file had been growing at a rapid rate. However, that log file was for failed login attempts, which meant some bot was constantly trying to log into the system, trying different usernames and passwords in random in a brute-force method.

Naturally something needed to be changed on that server to stop those unauthorized login attempts. (And also enable logrotate for that log file so that it wouldn't grow quite that much even in exceptional situations.)

Of course it is also possible the login entries are irrelevant to you, but I guess it is still a good think to ask, why in your system it is logging so much more. Apparently it normally shouldn't write so much log information.

If it’s to do with chromium it’s likely scanning all electronic devices in your house/street for any information it can scrape to send home to skynet. Seriously though, galaxy is using chromium? Even more reason to avoid it like the plague.

I just deleted a 770 GB cef log in my GOG Galaxy install. I didn't look at it, just deleted it. Then my wife wondered what it was and I found this thread.

770 GB. Ridiculous.

Edit:

Just started up the GoG Galaxy again and this is in the log now already:

[0317/092218.684:INFO:CONSOLE(1)] "%c09:22:18 %cINFO", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)
[0317/092218.684:INFO:CONSOLE(1)] "%c09:22:18 %cINFO", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)
[0317/092218.723:INFO:CONSOLE(1)] "%c09:22:18 %cINFO", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)
[0317/092221.035:INFO:CONSOLE(1)] "%c09:22:21 %cWARNING", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)
[0317/092221.457:INFO:CONSOLE(1)] "%c09:22:21 %cINFO", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)
[0317/092222.800:INFO:CONSOLE(1)] "%c09:22:22 %cINFO", source: file:///C:/Program%20Files%20%28x86%29/GOG%20Galaxy/web/client.js (1)

Just uninstall galaxy, no further problems!

My cef.log is a slim 1.07 MB. Timestamp says it was created a little over a year ago, and updated today.

If your log file size balloons out of control, be sure to click the cog wheel in GOG Galaxy and choose Report Issue. Until it's fixed, you could use something like Task Scheduler and a batch file to delete the file every once in a while.

Recently i had log files in the 100Gb size which was eating all the space on my laptop. Had to investigate using du -sh in order to narrow it down. Afterwards when a script restarts and is related to that log it deletes it, which is likely each time the computer needs to reboot (once every couple weeks)

I'm certain you can safely delete it, but you could also open it in a text editor and see. Though at 230Gb it would be much easier to use a basic UNIX tool or other and look at the head (or the top 100 lines) and see what it says. being a log file it's again probably text. It's probably minor errors warnings or notes of; Which includes a date, a time, short description, and some issue it had. It could be as benign as 'couldn't ping gog.com at this time' or it could be tons of 'download chunk is corrupt, retrying' or 'fatal error, can't get write permission to directory XYZ'... About what i expected. Though why they don't compress them i couldn't tell you, as it would reduce it probably 50:1. Or when it exceeds a certain size or on restarting the app changing the name and compressing it as some systems might do to save space.