PL/SQL Dev 13 does not quit completely

[vlevi]

Hello,
I realized, that PL/SQL Developer does not quit when I use my own plugin. When I delete this plugin dll, I have no problem with it.
The main exe disappears, but in Task manager, I see, that PL/SQL Developer stays in memory.
Win7x64, PL/SQL Developer 13.1
Can you help me, where should I start to investigate the problem?

 

[Marco Kalter]

When PL/SQL Developer quits it will call the CanClose, OnDeactivate, OnDestroy functions. Perhaps your Plug-In causes a problem in one of these functions?

 

[pavel_j]

I can confirm the same experience (PLSQL developer version 13, 32bit).

If I open process explorer after few days without restarting notebook, I can see one to several plsql developer processes even all instances were closed/terminated - there is not real instance running.

I haven't made any futher investigations. I have several plugins:

Plug-Ins
*Active Query Builder (C:\Program Files (x86)\PLSQL Developer 13\PlugIns\ActiveQueryBuilder.dll)
*CommentLines (C:\Program Files (x86)\PLSQL Developer 13\PlugIns\CommentLine.dll)
*PL/SQL Documentation (plsqldoc) (C:\Program Files (x86)\PLSQL Developer 13\PlugIns\plsqldoc.dll)
*rrProject (C:\Program Files (x86)\PLSQL Developer 13\PlugIns\rrPLDPlugin.dll)
*ToggleHeadBody (C:\Program Files (x86)\PLSQL Developer 13\PlugIns\ToggleHeadBody.dll)
(* is Active)

but I don't know if there plugins caused the problem.

Regards

 

[Nicolas D.]

If this can help --
I do not seems to experience any issue on my end with our custom plugin.

What I can suggest is that:
Add parameter to PL/SQL Developer Shortcut "DebugSQL" (if you want to get ALL SQL incl. from your plugin) or "DebugPlugins" (you just get PlugIns calls, but no SQL), run, do a few things, stop and check the logs.
Comparing your own plugin and the one provided with the software to see if anything misbehave or if you get an error somewhere.
You may also add some debug logging into your plugin code, that will appear in this log as well.

Also -- not sure if it help, but out plugin define and expose OnDestroy() function, even if I do not need it -- the function explicitly do nothing -- but it is present to be called. Maybe this can also help.

Analyze your log may give you hint where to look.
Also, test by disabling all plugins but one, it will help you targeting the culprit.

 

[vlevi]

Hello,
I tried to check if PL/SQL Dev quits, or not, but every time, I tried, it stopped normally
I tried to use without plugins, those plugins are necessary for my work, so I can use it only for minutes, and after this short period, the program exits normally, so I cannot examine the problem.
I will try the debugplugins parameter, maybe it helps.

 

[Nicolas D.]

Strangely, I did get it today -- I was having multiple instances running, I did stop them (to install the 13.0.1 fix 1, thanks Marco!) and installer told me there was 3 left open that I could not see.

I will monitor as well.
But it seems it take some time before it arise -- on short run to try to get the issue it stop properly.

 

[Nicolas D.]

Marco,

I did get another instance of PL/SQL developer that did not stop. Hard to debug right now. Can we have an update in next update to help debugging here?

My main issue is that I often have multiple instances open, but only one Debug.txt file.

Would it be possible to add the following option so we can have multiple debug from multiple instances:
If set DebugSQL or DebugPlugIns in command line, it would create "Debug.txt" file.
If specifying DebugSQL=Test1 or DebugPlugIns=Test1, it would create "Debug_Test1.txt" file instead - whatever the value it will alter the filename within that session so we can have as many copy as we need.

That would help a lot to see what is going on in this case and help you fixing it.

Thanks

 

[Nicolas D.]

Marco,

It is still happening in 13.0.2.
Of course, cannot get the feedback from debug as it never happen to the one I did put the debug on... Therefore could not get any detail yet on what prevent the binary to terminate properly.

Is my suggestion above could become a thing so we can hope to get some data for you?

 

[Nicolas D.]

Update

I was lucky today - it did fail on the one I was tracing this time! - I trace with DebugPlugIns for now.

Here is the end of the Debug.txt today:

02:18:55.924 PreferenceSet Filename = C:\Users\nicolasd\AppData\Roaming\PLSQL Developer 13\Preferences\NicolasD\user.prefs
02:18:55.924 PreferenceSet AltFile = user.prefs
02:18:55.926 PreferenceSet.Save end
02:18:55.927 Docking forms Destroying
02:18:55.928 MainForm Destroying
02:18:55.932 MainForm Destroyed
02:18:56.044 Finalization HTMLUnit
02:18:56.044 Finalization HTMLUnit done
02:18:56.052 Finalization PLSCommon
02:18:56.052 Finalization PLSCommon done
02:18:56.053 Finalization HTMLUnit
02:18:56.053 Finalization HTMLUnit done
02:18:56.054 Finalization DBObjectUnit

while a correct one I did save before end with:

04:43:37.319 MainForm Destroying
04:43:37.324 MainForm Destroyed
04:43:37.433 Finalization HTMLUnit
04:43:37.434 Finalization HTMLUnit done
04:43:37.442 Finalization PLSCommon
04:43:37.443 Finalization PLSCommon done
04:43:37.443 Finalization HTMLUnit
04:43:37.444 Finalization HTMLUnit done
04:43:37.444 Finalization DBObjectUnit
04:43:37.587 Finalization DBObjectUnit done
04:43:37.588 Finalization PlanUnit
04:43:37.589 Finalization PlanUnit done
04:43:37.589 Finalization RepUnit
04:43:37.590 Finalization RepUnit done
04:43:37.590 Finalization ReportCommon
04:43:37.591 Finalization ReportCommon done
04:43:37.593 Finalization StatUnit
04:43:37.593 Finalization StatUnit done
04:43:37.594 Finalization TotalRecallUnit
04:43:37.594 Finalization TotalRecallUnit done
04:43:37.595 Finalization RowExportUnit
04:43:37.595 Finalization RowExportUnit done
04:43:37.597 Finalization MacroUnit
04:43:37.598 Finalization MacroUnit done

Hope this will help a bit.
I keep tracing to see if this behavior is consistent over time.
See my previous message for a way to help trace it.

 

[Nicolas D.]

Update - It did happen again (Version 13.0.2) on one instance I am tracking, and it stop at the same place:

08:01:27.454 Finalization DBObjectUnit

Is the last message I get - DBObjectUnit never end - it did last that way all night long.

Marco, do you wish me to do anything else to try to figure out what is the issue?

 

[Nicolas D.]

Bumping this one up.
still happening in 13.0.5.

I have to kill lost processes from time to time.

 

[Marco Kalter]

Can you check again with the current 13.0.6 version? It includes a fix for this issue.

 

[Nicolas D.]

so far so good, no processes left since I updated to 13.0.6.

Thanks!