Markus Junginger

Another instance of this with v3.5.2: ``` WARNING: ThreadSanitizer: signal-unsafe call inside of a signal (pid=15007) #0 operator new(unsigned long) (libtsan.so.2+0x8d389) #1 void std::__cxx11::basic_string::_M_construct(char*, char*, std::forward_iterator_tag) (libstdc++.so.6+0x12fd0c) #2 reportFatal ../../catch2-src/src/catch2/internal/catch_fatal_condition_handler.cpp:62...

Digged a bit in the Catch2 sources; at least one of the issues is the string creation at the last line here: ```cpp void RunContext::handleFatalErrorCondition( StringRef message ) { //...

Well, as a workaround for sanitizer builds, I now disable Catch2 signal handling like this now: target_compile_definitions(Catch2 PRIVATE CATCH_CONFIG_NO_POSIX_SIGNALS)

> Such fields should not be returned as "null" but should preserve any values provided by the class'es default initialiser. This is not how it works or should work. If...

The property is null in the database. Please refrain from further comments. Thank you.

Again, you do not understand what is going on. Sorry, but you seem ignorant to what we have written. I do not consider this a fruitful conversation and we want...

Hey buddy, I'm feeling the same way. Hugs and kisses.

@greenrobot-team To pick up on the annotation, maybe this would be better? `@DefaultForNull(factory = MyValueProvider.class)` Where MyValueProvider would implement an interface "ValueProvider" which basically has a single method like `Object...

FYI: internally, we have the basic functionality in-place to "defragment" a database (e.g. reclaim free pages) by making a fresh copy. However, this still must be integrated with opening the...

We just released a Docker-based solution for that: https://docs.objectbox.io/data-browser#run-via-docker Please let us know if it works for you. Blog post will follow very soon.