Wednesday, January 24th 2018, 12:42pm UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

alfred-ai

Beginner

Date of registration: May 3rd 2017

Posts: 7

1

Friday, January 5th 2018, 9:56pm

[Ozone] Host memory usage jumped since V2.54

I have seen a steady increase of host memory usage with Ozone and it becomes unusable with the latest V2.54b. My environment is Ubuntu 16.04.3 LTS 64-bit running on Dell XPS 13 with 8GB of ram.

This is the memory usage as reported by Ubuntu's System Monitor (with same ELF loaded and the same Ozone configurations):
- V2.52d 3GB
- V2.54 3.5GB
- V2.54a 4GB
- V2.54b 4.3GB

This post has been edited 1 times, last edit by "alfred-ai" (Jan 5th 2018, 10:04pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

2

Monday, January 8th 2018, 1:54pm

Hello,

Thank you for your inquiry.
Such an issue is not known to us.
Could you make the used elf file available for us to be able to reproduce the issue?

Best regards,
Nino

alfred-ai

Beginner

Date of registration: May 3rd 2017

Posts: 7

3

Wednesday, January 10th 2018, 6:12pm

Sorry I won't be able to share the ELF. FYI our target is a Cortex-M7 running ~1MByte of (mostly) C++ code with FreeRTOS, compiled with the arm-none-eabi toochain.

Am I really the only one noticing this memory usage jump?

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

4

Thursday, January 11th 2018, 9:31am

Hello,

currently you are our first customer reporting any degradation in that regard.
With testprojects we were not able to reproduce the behaviour.
Could you create a example project where this issue is reproducible that you could share with us?
Without a reproduction scenario there is not much we can do.

Update: After some more testing we could see a difference with more complex elf files.
We already improved the behaviour which will be available in todays Ozone beta release V2.55: https://www.segger.com/downloads/jlink-beta/
Could you test that beta release out and see if this solves your problem as well?

Best regards,
Nino

alfred-ai

Beginner

Date of registration: May 3rd 2017

Posts: 7

5

Thursday, January 11th 2018, 5:23pm

I have just gave v2.55 beta a try. I see Ozone stalled and hoard 100% of one of the CPU cores while consume 2.6GB of ram.

Here is the link for the screenshot.

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

6

Thursday, January 11th 2018, 5:44pm

Hello,

Thanks for testing.
If Ozone has high CPU load just after opening the elf file, this is expected as Ozone first needs to parse the information.
Does the issue resolve when waiting a couple of seconds?
The screenshot shows a CPU usage of only 26%.
Is that a mistake?
Is now Ozone workable for you or still problematic?

Best regards,
Nino

alfred-ai

Beginner

Date of registration: May 3rd 2017

Posts: 7

7

Thursday, January 11th 2018, 6:06pm

Sorry I should have a bit more clear in my last reply. I left the Ozone beta running for more than 15 minutes and I called it stalled. About CPU usage, it shows 25% because it is only hoarding one of the CPU core (my XPS has a quad core Intel CPU).

One more data point is I have the FreeRTOS plug in enabled, i.e. "Project.SetOSPlugin("freeRTOSPlugin");" in the .jdebug file.

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

8

Monday, January 15th 2018, 9:37am

Hello,

This thread will be handled further per e-mail and PM.

Best regards,
Nino