rubberduck-vba / Rubberduck

Every programmer needs a rubberduck. COM add-in for the VBA & VB6 IDE (VBE).
https://rubberduckvba.com
GNU General Public License v3.0
1.92k stars 302 forks source link

Corel X4 crashes when opening IDE #2298

Closed Octopus134 closed 6 years ago

Octopus134 commented 8 years ago

After installing rubberduck 2.8, I tried to open the IDE in Corel Draw X4. Corel immediately crashes, not even seen anything of the IDE. I had to deinstall rubberduck. Win8.1-64, rubberduck 2.0.8.30557

Thomas

Vogel612 commented 8 years ago

Hi Tomas,

sorry to hear. Is there possibly any more information you could give us about how Corel crashed? Basically anything could help to fix this...

Thanks, Vogel

Octopus134 commented 8 years ago

Hi Vogel

I like to do, but how? I reinstalled rubberduck, started corel X4, tried to open the IDE by Extras > Makros > Makro editor (german version): Corel draw funktioniert nicht mehr. If I click on debugging there is looked for a file c:\users\Hosch...\rubberduckhooks.cs. WHile i am trying to find that on my PC in the downloaded code, there are many messages about missing pdbs. But my PC gets freezed and I have to hard-reset it. Even if I had the PDBs, I think I would not be able to do anything any more at that time.

if I unloaded rubberduck-Addin in the Access IDE (> Addins >AddinManager > loaded/unload ) start corel =OK Open the IDE = OK load rubberduck in the AddinManager: Crash

In Visual STudio there are 2 errors when I open the solution rubberduck (download today as a zipfile.)

Severity Code Description Project File Line Suppression State Error The command "eventcreate /ID 1 /L APPLICATION /T INFORMATION /SO "Rubberduck-VBA" /D "Deploying Rubberduck from Visual Studio Build"" exited with code 1. Rubberduck

Severity Code Description Project File Line Suppression State Error Metadata file 'D:\N\Quellcodeverwaltung\Rubberduck-next\RetailCoder.VBE\bin\Debug\Rubberduck.dll' could not be found RubberduckTests D:\N\Quellcodeverwaltung\Rubberduck-next\RubberduckTests\CSC

Thomas

Vogel612 commented 8 years ago

That already gives us a start. The problem seems to be situated in the class responsible for listening to key-combinations (here) apparently #1710 could be related.

It seems there used to be some bug that made Rubberduck roll over when reloaded from inside the VBE ... It might be a start. Thanks!

ThunderFrame commented 8 years ago

hmm, CorelDRAW X6 64-bit VBE fails to load Rubberduck. I don't think I've run Rubberduck in CorelDRAW since I reinstalled Corel, so I'm unsure what's causing this.

retailcoder commented 7 years ago

@ThunderFrame can you repro with 2.0.11?

ThunderFrame commented 7 years ago

My copy of CorelDRAW X6 was having problems (although it worked on a different computer many months ago). But I have Office XP, Visio 2003, Office 2016 and CorelDRAW X6 installed. I believe they all have their own version of the Office TLB - MSO.DLL (primarily for the CommandBar classes).

As per #2496, having 4 different versions of MSO.DLL as well as having updates in an inconsistent order, has likely put my registry entries in harm's way.

While running CorelDRAW as Administrator did help, Rubberduck does parse, but the status bar briefly says it's a Resolver Error before changing to say that it's a Parser Error (although no errors are listed in the window).

I seem to recall a similar problem when originally getting Rubberduck to work in CorelDRAW - I had to unload some/all of the Global Macros from within the Host UI, before opening the VBE and parsing. I need to investigate that further, but I'll raise a separate issue for that.

@Octopus134 Are you able to confirm if running X4 as Administrator helps? You may have a corrupted registry if you have CorelDRAW and any other Office product installed - See this SO answer for details http://stackoverflow.com/a/12962795/5757159

bclothier commented 6 years ago

Closing the issue since we changed both how we were installing the add in and executing code (cf #3836 and #3778 ). In theory, Rubberduck should now work on any host. If this is a issue still even with current release, open a new issue with more recent repro.