<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging &amp;quot;Backends flushed&amp;quot; while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39191/logging-backends-flushed-while-dropping-logs-is-counterproductive</link><description>This issue exists in SDK 15.2 and earlier. 
 In nrf_log_frontend_dequeue() when memobj cannot be allocated, the backend flush api is used to free memory. However this memory gets immediately consumed by a log WARNING log &amp;quot;Backends flushed&amp;quot; which seems</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 Apr 2022 13:10:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39191/logging-backends-flushed-while-dropping-logs-is-counterproductive" /><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/365599?ContentTypeID=1</link><pubDate>Fri, 29 Apr 2022 13:10:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c59eb733-18b0-42b8-845a-cbb53c89470f</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Yes, that is unfortunately the case. I have bumped the issue but I cannot promise that it will be fixed (particularly as the &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement"&gt;nRF5 SDK is in maintenance mode&lt;/a&gt;).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/365489?ContentTypeID=1</link><pubDate>Thu, 28 Apr 2022 22:45:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d54bf98-42e9-42ba-9f00-450ade050bca</guid><dc:creator>Anthony Ambuehl</dc:creator><description>&lt;p&gt;BTW this problem still exists in SDK 17.0.2&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/183987?ContentTypeID=1</link><pubDate>Fri, 26 Apr 2019 08:35:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0f9e22d-24a2-486e-b15f-33c3de7c2e4c</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;This is still there in SDK 15.3.0 and I&amp;#39;m hitting the same issue. Are you going to fix it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/152610?ContentTypeID=1</link><pubDate>Fri, 12 Oct 2018 07:58:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5717a942-6bcb-4c80-92c6-86f8c8d4ca34</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You are right, of course (I was too quick when I looked at this initially.) I will&amp;nbsp;report this internally.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/152399?ContentTypeID=1</link><pubDate>Wed, 10 Oct 2018 16:38:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be9955ef-bf0f-4318-8842-93f6e18355ca</guid><dc:creator>Anthony Ambuehl</dc:creator><description>&lt;p&gt;Once again... the backend flush does not drop all logs.&amp;nbsp; It only drops 1 log which gets replaced immediately with &amp;quot;Backends flushed&amp;quot;&amp;nbsp; I know this from direct experience.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/151870?ContentTypeID=1</link><pubDate>Fri, 05 Oct 2018 15:20:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:564225ad-df7c-48a3-b821-0ecc17e5cc60</guid><dc:creator>Anthony Ambuehl</dc:creator><description>&lt;p&gt;Backend flush drops a single log message.&amp;nbsp; This is not the same as NRF_LOG_FLUSH().&amp;nbsp; Dropping a single log message and then generating a new log message is counterproductive.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;For my code base I added an atomic counter for backend_flush() calls and report the number of flushes when the log buffer reaches empty.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging "Backends flushed" while dropping logs is counterproductive.</title><link>https://devzone.nordicsemi.com/thread/151817?ContentTypeID=1</link><pubDate>Fri, 05 Oct 2018 11:46:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:69b5ffa5-d709-40ef-a7b1-0b11c9541bea</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for your feedback. Personally, I think the current SDK implementation makes a lot of sense as it it can be very useful to see clearly where in the history logs were flushed. A flag does not do quite the same, as it will not show you &lt;em&gt;where&lt;/em&gt; there are missing logs. In any case it is written after the logs were flushed there should still be plenty of room for other logs after writing this short string (if not you could either shorten the string even more or use a larger buffer if you have available memory).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>