Boost C++ Libraries: Ticket #11729: Boost interprocess fails to initialize on long-running Windows machines https://svn.boost.org/trac10/ticket/11729 <p> This bug report is similar to <a class="ext-link" href="https://svn.boost.org/trac/boost/ticket/9767"><span class="icon">​</span>#9767</a>, but the effect described there is only part of the problem and the workaround described there may not always be applicable. </p> <p> On Windows Boost Interprocess tries to determine the last boot time by looking at the system event log. This may fail, if the machine has been running a longer time or if it has only been suspended instead of rebooting most of the time. The effect is, that Boost crashes, if the boot time cannot be determined. </p> <p> The workaround may not always be applicable, because a directory has to be hardcoded at compile time, which may not be accessible on all machines, where the resulting program is ever run. </p> <p> So I think that instead of the workaround described in <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/9767" title="#9767: Bugs: boost::interprocess bootstamp generation causes error in case of ... (closed: fixed)">#9767</a> a real solution should be implemented for this case. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11729 Trac 1.4.3 William Clements <William.Clements@…> Mon, 16 Nov 2015 21:36:19 GMT <link>https://svn.boost.org/trac10/ticket/11729#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11729#comment:1</guid> <description> <p> I saw a proposed solution in <a class="new ticket" href="https://svn.boost.org/trac10/ticket/11660" title="#11660: Bugs: interprocess::winapi::get_last_bootup_time(std::string &amp;stamp) fails, ... (new)">#11660</a> </p> </description> <category>Ticket</category> </item> <item> <author>martin.apel@…</author> <pubDate>Tue, 17 Nov 2015 08:03:20 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/11729#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/11729#comment:2</guid> <description> <p> The solution looks OK to me, though I'm not a Windows expert. Anyway I still wonder, if it's actually necessary to have the interprocess folder name include the boot timestamp. </p> </description> <category>Ticket</category> </item> </channel> </rss>