Access violation (a strange one)

[Marc Witsel]

Hi,

I haven't seen this before:

Access violation at address 00456918 in module 'PLSQLDev.exe'. Read of address 00098053.

Version of PLSQLDev is 5.0.3.527, running against 8.1.7.4.0 dll's, on a W2K.
It happens when I start PLSQLDev for the SECOND time, and try to switch the Schema Browser from anything to anything else. As soon as the mouse moves over the pulldown, it gives an access violation. Note, though, that PLSQLDev itself does not crash.
Other curiosa: changing the view in the browser in any other instance of PLSQLDev (1st, 3rd, etc) also causes the second instance to A.V.
Shutting down the 2nd instance cures it. But the next instance started will pick up this behaviour, also on behalf the the others.

Only unusual thing is that the installation was as a domain user (not as adminstrator, alas), and as the C drive is locked down, into a shared drive as well. But I've done these things before, shouldn't be a problem.

Obviously some contention problem, somewhere. Registry?

Marc

 

[Marco Kalter]

Nothing spectacular happens when you are accessing the Object Browser, so it's curious that this should cause an access violation.

Can you try the same with the current 5.1.4 release (trial or registered)? It will log a call stack which should help us find the cause of the problem. It can also be that this is already fixed in 5.1.4 of course.

 

[Marc Witsel]

Marco,

it must be fixed in 5.1.4. I just downloaded a trial version, and installed it in an identical way. No problems at all.
Now if only we had a licence for 5.1.x as well... Oh well, we pushed for it, we pushed hard, but corporate purchasing wouldn't budge. They bought TOAD. Yuk. Nobody uses it - we all still use our old PLSQLDev 5.0.2 for serious PL/SQL programming. People even set up Oracle Designer to call PLSQLDev instead of the built-in PL/SQL editor.
Anyway, is there any way I can get a stack trace for the 5.0.3? Like I said, there's no core, and the debugger doesn't notice it either.

 

[Marc Witsel]

Since installing 5.1.4, the problem has disappeared in 5.0.3.
The only thing I can think of is something in the registry, as the installations share the same registry tree.
Now to uninstall 5.1.4. There's no uninstall option, and as I did a user-install, it isn't in Add/remove Programs either. Guess I'll just remove the directory. Hmmm, just like UNIX....

 

[Marco Kalter]

If you installed it normally, there should be an entry in "Add/Remove Programs". This allows you to uninstall 5.1.4.