Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

atom -h throws CFAllocator messages #1627

Closed
bnferguson opened this issue Feb 28, 2014 · 3 comments · Fixed by #1660
Closed

atom -h throws CFAllocator messages #1627

bnferguson opened this issue Feb 28, 2014 · 3 comments · Fixed by #1660
Labels

Comments

@bnferguson
Copy link

A error/debug message is printed when running `atom -h`:

$ atom -h
2014-02-26 19:29:14.825 Atom[66299:507] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
Atom Editor v0.59.0

Usage: atom [options] [file ...]

Options:
-d, --dev Run in development mode. [boolean]
-f, --foreground Keep the browser process in the foreground. [boolean]
-h, --help Print this usage message. [boolean]
-l, --log-file Log all output to file. [string]
-n, --new-window Open a new window. [boolean]
-s, --spec-directory Set the directory from which specs are loaded (default: Atom's spec directory). [string]
-t, --test Run the specified specs and exit with error code on failures. [boolean]
-v, --version Print the version. [boolean]
-w, --wait Wait for window to be closed before returning. [boolean]

From: support/85cfec129f4f11e39023acbff144d3b9

@bnferguson bnferguson added the bug label Feb 28, 2014
@zcbenz
Copy link
Contributor

zcbenz commented Mar 1, 2014

I'll suppress this in libchomiumcontent, it seems that most users just thought it is a critical error.

@bnferguson
Copy link
Author

🤘 Thanks!

@lock
Copy link

lock bot commented Jan 26, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants