id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 14613,race issue loading plugins when editor already destroyed,Brian,Tade0,"See end of description for suggested fix. == Steps to reproduce == Find attached index.html which loads CKEditor script async and creates instance of ckeditor before quickly destroying the instance. To repo, place index.html in a directory along with the root ckeditor folder containing the source. Directory should look like: / |--index.html |--ckeditor |----ckeditor.js Load index.html and open chrome developer tools. Press button (sometimes takes a few times). You will hopefully see `ckeditor.js:formatted:16963Uncaught TypeError: Cannot read property 'customConfig' of undefined` == Expected result == Race conditions should be handled accordingly. == Actual result == Plugin tries to load after editor.status === 'destroyed' and is unable to reference the editor instance. == Other details (browser, OS, CKEditor version, installed plugins) == My guess for the fix is in core/editor.js:596 the plugin loader's call back should check if editor.status === 'destroyed' and simply return. However there may need to be more clean up but this is my simple fix to prevent us from running into this issue. Maybe you all will have a more elegant solution :)",Bug,review,Normal,,General,4.5.0,,race,