Copied and pasted some code to reproduce the issue. Hopefully it makes some 
sense... receiverLoop1 is increasing mem usage, receiverLoop2 does not.

Btw, set_rx_iq_balance function seems to be inverted, setting it to false on 
the E310 reduces spectrum images more than 50 dB, while true reduces only about 
24 dB...

https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1cMLXzNLpkkhBQ9gtFgeZgm-8N3v-OEFd%2Fview%3Fusp%3Ddrivesdk&data=04%7C01%7Cjsk%40nkom.no%7Cf5e97e128b734e566f5308d9aeb928b6%7Cad83e65c03f64cfdb79947a2fafd7bce%7C0%7C0%7C637732932540044724%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=d4z5DA9RGIP1MSe1JCD9njDShyl7o19JAP8lXtl3Op0%3D&reserved=0



________________________________
Fra: Jonathon Pendlum <jonathon.pend...@ettus.com>
Sendt: tirsdag 23. november 2021, 19:23
Til: Marcus D Leech
Kopi: Skorstad, Jørn; usrp-users@lists.ettus.com
Emne: Re: [USRP-users] Re: UHD 4.1 memory leak?

Hi Jorn,

Can you provide an example program we can use to reproduce the issue?

Jonathon

On Tue, Nov 23, 2021 at 12:44 PM Marcus D Leech 
<patchvonbr...@gmail.com<mailto:patchvonbr...@gmail.com>> wrote:
This looks like it might be a bug to me.



Sent from my iPhone

On Nov 23, 2021, at 6:00 AM, Skorstad, Jørn <j...@nkom.no<mailto:j...@nkom.no>> 
wrote:


Hello,

I have some trouble using the UHD 4.1.0.2 library. I am using RFNOC blocks 
RADIO and DDC, and setting up an RX stream using graph->create_rx_streamer. The 
receiver loop is running in its own thread doing something like this 
(simplified):

uhd::stream_cmd_t stream_cmd(uhd::stream_cmd_t::STREAM_MODE_NUM_SAMPS_AND_MORE);
stream_cmd.num_samps  = size_t(sampsPerBuff);
stream_cmd.stream_now = true;
stream_cmd.time_spec  = uhd::time_spec_t();

for (;;) {
  rx_stream->issue_stream_cmd(stream_cmd);
  rx_stream->recv(&buffer.front(), sampsPerBuff, md, 3.0, false);
  std::this_thread::sleep_for(std::chrono::milliseconds(2));
}

I am developing for an E310 sg3.

When calling issue_stream_cmd repeatedly this way memory usage goes up until 
resources are depleted (few hours). If stream_cmd is replaced with 
STREAM_MODE_START_CONTINUOUS and called just once memory usage is normal. But 
for the application developed the mode NUM_SAMPS_AND_MORE is better suited. It 
is also what we used with the 3.14.1 library, without any memory problems like 
this.

Any tips?

BR
Jorn


_______________________________________________
USRP-users mailing list -- 
usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to 
usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com>
_______________________________________________
USRP-users mailing list -- 
usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to 
usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com>

_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to