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

OOM errors #388

Open
emarsman opened this issue Jun 16, 2017 · 1 comment
Open

OOM errors #388

emarsman opened this issue Jun 16, 2017 · 1 comment

Comments

@emarsman
Copy link
Member

With increased memory for multi-frame diagnostics (1287437), devices can run out of memory when processing large amounts of CAN messages (

debug("JSON object is NULL -- probably OOM");
).

Current master works fine for diagnostics, but issues with large amounts of CAN traffic.

Related to #375.

@emarsman
Copy link
Member Author

can-oom branch makes this better. Works for standard translated signals. Full bus raw CAN still locks up device (Ref VI, works on C5). Could be running into this problem?

// In normal operation, if no output interface is enabled/attached (e.g.

Need to investigate further.

@emarsman emarsman mentioned this issue Jun 19, 2017
emarsman added a commit that referenced this issue Jun 19, 2017
reduce queue size to resolve memory errors. Tests updated as well. Temporary update to alleviate some of #388.
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

No branches or pull requests

1 participant