DICOM @ OFFIS

No, there is no way to prevent this, because DCMTK cannot know how much memory can be allocated safely (that would require very operating system specific code). DCMTK expects the new operator to return NULL in this case (because we are using the non-throwing version), and will in this case return an...

Weird. Perhaps you can check if in dcmdata/libsrc/dcdictbi.cc the code branch following #if DCM_DICT_DEFAULT == DCM_DICT_DEFAULT_USE_BUILTIN is compiled. This array is the built-in data dictionary that should but apparently is not present in your compiled code.

DcmElement::newValueField() explicitly uses operator new (std::nothrow) , and has been doing so in all DCMTK versions since 2009. If the new handler still throws an exception, this is due either to a compiler bug, or to a user-specific new handler being installed that ignores std::nothrow. MFC is k...

1. Is it normal for DcmFileFormat::loadFile() to take longer depending on the DICOM file size (or number of fragments)? Yes. While DCMTK will not read the entire file into memory, it needs to analyze the structure and skip (seek) over larger chunks of pixel data. While this is faster than reading t...

I would classify this as a bug. Note that the TLS support in dcmqrscp is new (introduced with the current version 3.6.9), and the movescu command line tool does not yet support TLS at all. This may explain why nobody has noticed this yet. Currently dcmqrscp indeed opens move sub-associations using u...

Thanks for the suggestion. I have just committed the improved description to our testing branch. This should become visible in the public git in a couple of days.

The documentation for BUILD_SHARED_LIBS says that if enabled the setting overrides the value of DCMTK_COMPILE_WIN32_MULTITHREADED_DLL , which is set to ON, i.e. in this case DCMTK is compiled with /MD or /MDd, respectively. If you have suggestions on how to make the wording easier to understand or c...

When you combine libraries compiled with a different runtime model, the Windows linker will issue a warning about incompatible runtime libraries. If you don't see that, everthing should be fine.

This is not what should be happening, but I suspect that the problem is on the fo-dicom side. The protocol for closing a DICOM network association requires one side (usually the client, as with findscu or echoscu) to send an A-RELEASE-RQ message to the server, indicating the wish to close the networ...

I think that this behaviour might be related to the use of MFC. As far as I know, the MFC comes with it's own implementation of operator new that calls AfxThrowMemoryException() if a block of memory cannot be allocated. Perhaps this implementation also ignores std::nothrow. Adjusting the link order ...

IPv6 support is not high on the list of priorities for the development team, the main reason being that our network infrastructure is IPv4 only, which makes it very difficult to develop and debug this. Unless somebody provides a patch / pull request for adding server-side IPv6 support, I do not see ...

The "unrecognized PDU type" message indicates that something that is not DICOM tries to connect to that port.
The timeout might be caused by an attempt to look up the hostname using a reverse DNS lookup. Try running storescp with the --disable-host-lookup option.

When writing a new DICOM file, the meta-header will be re-created from scratch, unless you use certain options in DcmFileFormat::saveFile(). Specifically, the implementation class UID and version name refer to the "implementation" that has written the file, which is DCMTK for the new file....

If I remember correctly, it should be possible to write a DICOM file in a different transfer syntax without all data getting loaded, as long as both the original transfer syntax and the new one are uncompressed (or Deflate). It should be easy for you to test this. Just don't call loadAllDataIntoMemo...

However, I have one more question—why was it working in Debug mode before enabling this setting?

Very good question. That should have produced the same error as in your release build.