Hi,<div><br></div><div>I am currently struggling with a crash that I find very hard to isolate. Please see attached three classes I am using (the one not included is FlamTimeMillis, but that is basically just my own time class).</div>
<div><br></div><div>In any case, LiveTimer works absolutely fine in my unit tests. It works absolutely fine in both debug and regular release versions. However, when compiled under msvc with compile options /Ox /Oi /Ot /GL and linked with /LTCG (e.g. whole program optimization), it crashes. But only in my main program, and not in any test I try to create. But in the main program, it consistently crashes.</div>

<div><br></div><div>According to the logs, it crashes between 3 and 4, e.g. the log looks like this:</div><div><br></div><div><div>IN: : LiveTimer: RegisterTimedCallback 2011-12-12 07:02:00.000000: Locked mutex.</div><div>

IN: : LiveTimer: Expires from now -22405.5 A: 2011-12-12 07:02:00.000000 B: 2011-12-12 13:15:25.489000 C: -2.24055e+007</div><div>IN: : 1</div><div>IN: : 2</div><div>IN: : 3</div></div><div><br></div><div>This happens on the very first call to RegisterTimedCallback. Judging from it, it looks like it crashes on timer.expires_from_now(boost::posix_time::seconds((long)secondsToElapse)). I checked that I am in the correct LiveTimer, and that LiveTimer still exists. I tried loading the dump file into WinDbg, and I get the following output:</div>

<div><br></div><div><br></div><div><div>XCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)</div><div>ExceptionAddress: 77b68da9 (ntdll!RtlpWaitOnCriticalSection+0x000000bd)</div><div>   ExceptionCode: c0000005 (Access violation)</div>

<div>  ExceptionFlags: 00000000</div><div>NumberParameters: 2</div><div>   Parameter[0]: 00000001</div><div>   Parameter[1]: 00000114</div><div>Attempt to write to address 00000114</div><div><br></div><div>PROCESS_NAME:  Test.exe</div>

<div><br></div><div>ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.</div><div><br></div><div>EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.</div>

<div><br></div><div>EXCEPTION_PARAMETER1:  00000001</div><div><br></div><div>EXCEPTION_PARAMETER2:  00000114</div><div><br></div><div>WRITE_ADDRESS:  00000114 </div><div><br></div><div>FOLLOWUP_IP: </div><div>Test!boost::asio::detail::win_iocp_io_service::cancel_timer&lt;boost::asio::time_traits&lt;boost::posix_time::ptime&gt; &gt;+4c [c:\program files (x86)\boost_1_47_0\boost\asio\detail\impl\win_iocp_io_service.hpp @ 117]</div>

<div>0139784c b001            mov     al,1</div><div><br></div><div>MOD_LIST: &lt;ANALYSIS/&gt;</div><div><br></div><div>NTGLOBALFLAG:  0</div><div><br></div><div>APPLICATION_VERIFIER_FLAGS:  0</div><div><br></div><div>FAULTING_THREAD:  000029b8</div>

<div><br></div><div>BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE</div><div><br></div><div>PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_DEREFERENCE</div><div><br></div><div>DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE</div>

<div><br></div><div>LAST_CONTROL_TRANSFER:  from 77b68cb8 to 77b68da9</div><div><br></div><div>STACK_TEXT:  </div><div>0032ec44 77b68cb8 00000000 00000000 00000000 ntdll!RtlpWaitOnCriticalSection+0xbd</div><div>0032ec6c 0139784c 00953408 654f7f27 0032ecf0 ntdll!RtlEnterCriticalSection+0x150</div>

<div>0032ecac 0139e79a 0095015c 0032f93c ffffffff Test!boost::asio::detail::win_iocp_io_service::cancel_timer&lt;boost::asio::time_traits&lt;boost::posix_time::ptime&gt; &gt;+0x4c [c:\program files (x86)\boost_1_47_0\boost\asio\detail\impl\win_iocp_io_service.hpp @ 117]</div>

<div>0032ecdc 013d9d20 0095015c 0032ed38 00000000 Test!boost::asio::detail::deadline_timer_service&lt;boost::asio::time_traits&lt;boost::posix_time::ptime&gt; &gt;::expires_from_now+0x6a [c:\program files (x86)\boost_1_47_0\boost\asio\detail\deadline_timer_service.hpp @ 159]</div>

<div>0032ecfc 013d948f 0032ed28 654f7e57 0095716c Test!boost::asio::basic_deadline_timer&lt;boost::posix_time::ptime,boost::asio::time_traits&lt;boost::posix_time::ptime&gt;,boost::asio::deadline_timer_service&lt;boost::posix_time::ptime,boost::asio::time_traits&lt;boost::posix_time::ptime&gt; &gt; &gt;::expires_from_now+0x30 [c:\program files (x86)\boost_1_47_0\boost\asio\basic_deadline_timer.hpp @ 411]</div>

<div>0032ede0 013b1840 0032f900 00950188 0094f970 Test!Flam::Live::LiveTimer::EnqueueTimedCallback+0x33f [c:\users\florian\documents\liveenvv1\trunk\flamlib\live\livetimer.cpp @ 55]</div><div><br></div><div><br></div><div>

STACK_COMMAND:  ~0s; .ecxr ; kb</div><div><br></div><div>FAULTING_SOURCE_CODE:  </div><div>   113:   // If the service has been shut down we silently ignore the cancellation.</div><div>   114:   if (::InterlockedExchangeAdd(&amp;shutdown_, 0) != 0)</div>

<div>   115:     return 0;</div><div>   116: </div><div>&gt;  117:   mutex::scoped_lock lock(dispatch_mutex_);</div><div>   118:   op_queue&lt;win_iocp_operation&gt; ops;</div><div>   119:   std::size_t n = queue.cancel_timer(timer, ops, max_cancelled);</div>

<div>   120:   post_deferred_completions(ops);</div><div>   121:   return n;</div><div>   122: }</div><div><br></div><div><br></div><div>SYMBOL_STACK_INDEX:  2</div><div><br></div><div>SYMBOL_NAME:  Test!boost::asio::detail::win_iocp_io_service::cancel_timer&lt;boost::asio::time_traits&lt;boost::posix_time::ptime&gt; &gt;+4c</div>

<div><br></div></div><div><br></div><div><br></div><div>The source quoted is from \boost_1_47_0\boost\asio\detail\impl\win_iocp_io_service.hpp.</div><div><br></div><div>Despite the fact that I can&#39;t isolate the error, everything I look at points to a problem somewhere within boost asio, or me not using asio correctly. Anyone any suggestions as to where to go from here? Would be much appreciated. What looks a bit suspicious to me (but that might be entirely wrong), is the line &quot;// If the service has been shut down we silently ignore the cancellation.,&quot; because the error happens after the return statement linked to that comment was apparently not executed, and the service has actually been shut down.</div>

<div><br></div><div><br></div><div><br></div><div>P.S. I know that I don&#39;t need to manage the queue myself and could just let asio handle it, however, eventually I would like to manage the queue more (e.g. edit some timers, cancel others, so I&#39;d prefer to stick to a single timer and manage the queue myself).</div>

<div><div><br></div><br>
</div>