My installation of Delphi XE7 update 1 Professional crashes after several minutes, without any user interaction. Just start the IDE, load a project, sit back and stare on the screen. After some minutes... Windows reports an application error and the only option is to quit the IDE.
My installation of Delphi XE7 update 1 Professional crashes after several minutes, without any user interaction. Just start the IDE, load a project, sit back and stare on the screen. After some minutes... Windows reports an application error and the only option is to quit the IDE.
Looking into the Windows Event Viewer, the name of the faulty application is bds.exe Version: 21.0.xxx, and the name of the faulty module is designide230.bpl, Version: 23.0.xxx
Yes, there is also Delphi 10 Seattle installed on the same machine, but why does XE7 loads a module from that other version? I can see that XE7 loads that module by clicking Help -> About -> Version information). That list shows that both designide210.bpl and designide230.bpl are loaded!
And I think that some copy protection code in XE7 stumbles about this and crashes the IDE.
Any ideas how to solve that problem?
I guess there is a package or expect DLL that was linked against 10 Seattle's (designide.)dcp.
ReplyDeleteCan you run Delphi under Delphi, and trace the module load to find out what's causing it to be loaded?
ReplyDeleteNot sure if this actually helps here, but in such a case I usually kick out anything that does not exist in a plain vanilla Delphi installation (export registry keys Experts and Known Packages, then delete all 3rd party entries). Then step by step re-enable each of its own.
ReplyDeleteAfter some research I found that designide230.bpl is listed in XE7 registry key HKEY_CURRENT_USER\Software\Embarcadero\BDS\15.0\Known Packages
ReplyDeleteI have now delete that entry; XE7 starts up normal and does no longer list that module as loaded. I've no idea how it got there.
Thanks for all the feedback!
Broken third-party installer?
ReplyDelete