1 / 5

Memory leaking in QMSS ?

Memory leaking in QMSS ?. Conditions. Refer to this e2e thread. To recreate the issue, please use the packages attached to this e2e thread. Run core0/1 first, an then core3 ….

belle
Download Presentation

Memory leaking in QMSS ?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Memory leaking in QMSS ?

  2. Conditions • Refer to this e2e thread. • To recreate the issue, please use the packages attached to this e2e thread.

  3. Run core0/1 first, an then core3 … ② Next, start Core3 (NDK client). NDK will try to insert memory to QMSS region 1 in its initialization phase. This snap shot is showing, core3 is trying to insert the descriptor @0x1380000～ into region1. Now put F5 !!! Once this line is executed, the next slide happened. ① Core0/1 (SRIO loopback) is started. As you see, core0 is working correctly. Note that Core0 is using the descriptor @0x1083xxxx～

  4. Result: Core0 starts to get the descriptor @ 0x1380xxxx! This address range is the descriptor on core3. Eventually, Core3 can hang-up.

  5. Questions • It looks like leaking memory between region0 and region1. Why this can happen ? • Is this QMSS bug ?

More Related