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.

Sign up for GitHub

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

Jump to bottom

No memory information with JERRY_FLAG_MEM_STATS #242

Closed
seanshpark opened this issue Jun 26, 2015 · 5 comments
Closed

No memory information with JERRY_FLAG_MEM_STATS #242

seanshpark opened this issue Jun 26, 2015 · 5 comments
Labels
question Raised question

Comments

@seanshpark
Copy link
Contributor

There used to be heap usage report when JERRY_FLAG_MEM_STATS was given.
Current code seems does not show them. Is it accidentally removed or intended?
@seanshpark seanshpark added the question Raised question label Jun 26, 2015
@ILyoan
Copy link
Contributor

ILyoan commented Jun 26, 2015

I think we need to turn off JERRY_DISABLE_HEAVY_DEBUG to see it.

@ruben-ayrapetyan
Copy link
Contributor

After commit jerryscript-project/iotjs@5f74d08 ReleaseJerry is not called before process exit, so process exits without calling jerry_cleanup, and memory statistics are not printed.
Before the commit heap usage report is printed.

@ILyoan ILyoan mentioned this issue Jun 29, 2015
Closed
@ILyoan
Copy link
Contributor

ILyoan commented Jun 29, 2015

I'll fix the exit before cleanup problem. Let's see if stats are printed out properly after land the patch.

@seanshpark
Copy link
Contributor Author

@ruben-ayrapetyan , thank you!

@seanshpark
Copy link
Contributor Author

As this question is solved and reason is not of JerryScript, I'll close this issue.

This was referenced May 17, 2020
Closed
Closed
This was referenced Oct 20, 2020
Closed
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Raised question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ILyoan @seanshpark @ruben-ayrapetyan