Because it seemed very strange to me that such a problem would only occur with a specific image, I gradually cleaned up a copy of my affected image today. Despite multiple attempts, I can't really tell in detail what was the problem, but somewhere in my image I had a months-old object explorer on DependentsFields open, and when I close it as well as a few other browsers/workspaces, the problem suddenly disappeared at the next VM restart and module loading works again.
This solves my concrete problem, but not the bug in general, so I would like to continue to investigate. However, after a number of attempts, my debug build of the VM does not any longer fail to find the module (though the release VM still does), so, unfortunately, I cannot continue my experiments right now.
@marceltaeumel I already did some research on this error but did not really find something interesting. Circular dependencies could be a reason, but from what I could find out, the ordered list of loaded modules does not differ between my defect and my cleaned-up image, so this would not make sense. There were also mentioned some other points such as security limitations (memory protection/DEP/ESP, never heard of that before), but I would be surprised if such a mechanism would only take effect sporadically.
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.