Closed mmmovania closed 2 years ago
Thanks for reporting this! Didn't expect a clock_cast
to error out like that (on just some systems on top of that).
I'll implement your fix and push a hotfix release!
In the interim, could you share the contents of the system_exception
you're getting? I'd be curious what the underlying error message is to maybe fix the issue in a more elegant way.
Reverting to Apple behavior is a bit unfortunate, because the term T::clock::now() + system_clock::now()
is not guaranteed to call now()
at the same time for both clocks -- so the resulting time_t
will randomly fluctuate. Not that it matters much... this function is only used to display timestamps up to 1s accuracy, but it still irks me a little.
The following is printed on console.
Caught exception in main loop: The specified module could not be found
The Output windows spits this.
Exception thrown at 0x00007FF95C727AFC in tev.exe: Microsoft C++ exception: std::system_error at memory location 0x0000004DCAEA9620.
Exception thrown at 0x00007FF95C727AFC in tev.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
Exception thrown at 0x00007FF95C727AFC in tev.exe: Microsoft C++ exception: std::system_error at memory location 0x0000004DCAEA9620.
Thank you! This unfortunately doesn't shed a lot of light on the issue... oh well. The hacky approach it is. :)
Just to let you know the error is thrown at line 3153 chrono header //3153 const auto& _Tzdb = _CHRONO get_tzdb();
Hi i noticed an issue in the to_time_t function defined in Image.cpp. I was trying to use the latest version of tev on pbrtv4 on Win8.1 and tev crashed. I managed to dig the reason and its the to_time_t function. Currently its defined as follows:
which causes a system_exception and crashes on Win8.1 VS 2019. I managed to fix it by changing it to this which basically treats both windows and apple the same way.