<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Am 30.10.18 um 08:37 schrieb Hermann Meyer: </div> <blockquote type="cite" cite="mid:a631cb2b-a7ab-b496-b9e8-511d0fc7b2ff@web.de"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <div class="moz-cite-prefix">Am 29.10.18 um 15:34 schrieb Robin Gareus: </div> <blockquote type="cite" cite="mid:851109dd-df32-e9c1-33b9-97776ee1439f@gareus.org"> <blockquote type="cite" style="color: #000000;"> <pre class="moz-quote-pre" wrap="">The plugins already loaded into memory should still hopefully be OK. </pre> </blockquote> <pre class="moz-quote-pre" wrap="">yep. On Unix systems already loaded .so will be kept in memory. On Windows you cannot write/replace to a file that is currently opened. You can skip and postpone scanning of plugins that are currently in use until the next session load. </pre> </blockquote> During plugin development I check plugins usually (first) in jalv. Sometimes I forgot that I've loaded a plug already and update it, result is always a crash in jalv. The same happen in Mixbus4, I've just checked it, out of curiosity. </blockquote> True, there is no problem when the update didn't happen in-place, means remove the older bundle and then install the new one ( like most package mangers does). </body> </html>