14.0.6 beta freezes sometime

vlevi

Member³
I don't know extacly when, and why, but the beta had frozen, while I did nothing special.
Maybe copied a text, or something else, and PL/D stooped responding.
I did not get any error message, it justs hangs forever, and it uses 100% CPU on 1 core (other 5 CPU cores are normal)

I'm afraid to use it, because I can loose my edited texts :(
 
I have encountered the same behavior.

For me it has happened 3-4 times, each time when I was typing a select in an SQL window. Suddenly in the middle of typing e.g. a column name, PLD freezes totally. I have not noted the CPU usage, but I will check for that if/when it happens again.

Could it have something to do with PLD trying to perform code completion?
 
No. Instead of restarting it, I started PL/SQL Dev 13. Maybe an hour later, the PL/SQL Dev.14 window was st
 
To obtain some more diagnostic information, can all of you who have experienced this modify the PL/SQL Developer shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer 14 Beta\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 14 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 14).

If the debug.txt file is too big to send, just send the last 1000 lines of the file.

We would also like to know the following information from those who have experienced this:
  1. Does the error occur during typing? Or randomly?
  2. If it happens during typing, does it happen while making a text selection?
  3. Is there a specific window type involved (SQL Window, Program Window, ...)?
  4. Did you have multiple PL/SQL Developer instances opened when this happened?
  5. Approximately how long had the PL/SQL Developer instance been running when this happened?
  6. Did you have a Workset opened when this error occurred?
  7. Are you using the version control integration for Git or Subversion?
  8. Can you let us know if the following preference settings were enabled?
    • Oracle / Connection / Check connection
    • Oracle / Connection / Check all Sessions
    • Files / Backup / Save on time interval
  9. Has this happened before in version 14.0 Beta 5 or earlier?
  10. Has this happened before in version 13.0 or earlier?

 
Last edited:
I noticed this as well some days ago. Sorry, I didn't generate a debug file. But for me, it seem to happen, when I made a typo in an object name and PLD tries to find more infos about this object: example - trying to find a columnname of a misspelled table. Or wrong package-> find procedures.
Not always, but when it happened to me, it happened in such a situation.
Perhaps this hint helps a bit
Best regards
Joachim
 
I will try it.
Yesterday I had a freeze, but I forgot to use the debugsql parameter.
From this morning I will use it, but it didn'n froze yet.

BTW, I love the new file compare dialog, and the multiple result sets in the SQL Window.

 
Stuck again, luckily, I wasn't in any production, I only tried to reproduce the problem, and I succeed.

Where can I upload the debug.txt?
I think, there is nothing :(
00:34:35.799 TOracleQuery $065744A0 Start Query.Execute
This is where I started the query, it is not a difficult select.
00:34:35.751 TOracleQuery SQLForm_1.TestQuery Start Query.Describe
SELECT * FROM atg_berterv_elem_szamitas_mod
Later I added some where clause, and the PL/SQL Developer stopped suddenly :(

The last few rows are :

00:34:35.713 SQLForm Executing...
00:34:35.728 GotoQueryTab 0
00:34:35.729 GotoQueryTab: QueryTabControlChanging
00:34:35.729 GotoQueryTab: QueryTabControlChange
00:34:35.730 QueryTabControlChange: Grid
00:34:35.730 QueryTabControlChange: Show EditPanel 1
00:34:35.732 QueryTabControlChange: Hide Grids 1
00:34:35.732 QueryTabControlChange: Hide Grids 2
00:34:35.733 QueryTabControlChange: GetTableName
00:34:35.733 QueryTabControlChange: SQLMessage =
00:34:35.734 GotoQueryTab done
00:34:35.734 SQLForm Executing...
00:34:35.738 TSQLThread SQLThread Suspend ended
00:34:35.739 TSQLThread SQLThread runs
00:34:35.739 TSQLThread SQLThread loop start
00:34:35.740 Lock
00:34:35.741 TOracleQuery Query Start Query.Execute
SQL = begin :id := sys.dbms_transaction.local_transaction_id; end;
:ID = Null
00:34:35.742 TOracleQuery Query End
Duration = 0
00:34:35.743 TOracleQuery $06572A80 Start Query.Execute
SQL = select a.n_szamitasmod,a.c_nev1 from
atg_berterv_elem_szamitas_mod a
where 1=2
00:34:35.746 UnLock
00:34:35.747 TOracleQuery $06572A80 End (0 records processed)
Duration = 0
00:34:35.751 TOracleQuery SQLForm_1.TestQuery Start Query.Describe
SQL = SELECT * FROM atg_berterv_elem_szamitas_mod
00:34:35.754 TOracleQuery SQLForm_1.TestQuery End
Duration = 0
00:34:35.755 TSQLThread SQLThread loop end
00:34:35.756 TSQLThread SQLThread loop done
00:34:35.757 TOracleQuery Query Start Query.Execute
SQL = begin :id := sys.dbms_transaction.local_transaction_id; end;
:ID = Null
00:34:35.758 TOracleQuery Query End
Duration = 0
00:34:35.758 TSQLThread SQLThread transaction management done
00:34:35.759 TSQLThread SQLThread Postmessage
00:34:35.760 TSQLThread SQLThread Suspend
00:34:35.760 TSQLForm.ThreadFinished
00:34:35.761 TSQLForm.ThreadFinished: SQLThread.Suspended
00:34:35.761 SQLForm [14:27:37] 0 rows selected in 0,016 seconds||ThreadFinished
00:34:35.763 Lock
00:34:35.764 UnLock
00:34:35.768 TOracleSession $079956A0 Start Session.Commit
00:34:35.769 TOracleSession $079956A0 End
Duration = 0
00:34:35.782 Lock
00:34:35.783 UnLock
00:34:35.784 TOracleQuery Query Start Query.Execute
SQL = begin :id := sys.dbms_transaction.local_transaction_id; end;
:ID = Null
00:34:35.785 TOracleQuery Query End
Duration = 0
00:34:35.786 Lock
00:34:35.790 UnLock
00:34:35.791 NavigationBookmarks.EnableButtons(Rebuild)
00:34:35.792 NavigationBookmarks: Backward=10, Forward=0
00:34:35.792 WindowAllowed(3)
00:34:35.793 WindowAllowed done
00:34:35.793 WindowAllowed(2)
00:34:35.794 WindowAllowed done
00:34:35.795 WindowAllowed(6)
00:34:35.795 WindowAllowed done
00:34:35.796 WindowAllowed(4)
00:34:35.796 WindowAllowed done
00:34:35.797 WindowAllowed(5)
00:34:35.797 WindowAllowed done
00:34:35.799 TOracleQuery $065744A0 Start Query.Execute
SQL = declare
Lines sys.dbms_output.chararr;
begin
:NumLines := 10;
sys.dbms_output.get_lines(lines => Lines, numlines => :NumLines);
if :NumLines > 0 then :Line0 := Lines(1); end if;
if :NumLines > 1 then :Line1 := Lines(2); end if;
if :NumLines > 2 then :Line2 := Lines(3); end if;
if :NumLines > 3 then :Line3 := Lines(4); end if;
if :NumLines > 4 then :Line4 := Lines(5); end if;
if :NumLines > 5 then :Line5 := Lines(6); end if;
if :NumLines > 6 then :Line6 := Lines(7); end if;
if :NumLines > 7 then :Line7 := Lines(8); end if;
if :NumLines > 8 then :Line8 := Lines(9); end if;
if :NumLines > 9 then :Line9 := Lines(10); end if;
end;
:NUMLINES = Null
:LINE0 = Null
:LINE1 = Null
:LINE2 = Null
:LINE3 = Null
:LINE4 = Null
:LINE5 = Null
:LINE6 = Null
:LINE7 = Null
:LINE8 = Null
:LINE9 = Null
00:34:35.800 TOracleQuery $065744A0 End
Duration = 0
00:34:35.804 GotoQueryTab 0
00:34:35.805 GotoQueryTab: QueryTabControlChanging
00:34:35.806 GotoQueryTab: QueryTabControlChange
00:34:35.807 QueryTabControlChange: Grid
00:34:35.808 QueryTabControlChange: Show EditPanel 1
00:34:35.809 QueryTabControlChange: Hide Grids 1
00:34:35.810 QueryTabControlChange: Hide Grids 2
00:34:35.810 QueryTabControlChange: GetTableName
00:34:35.811 QueryTabControlChange: SQLMessage = [14:27:37] 0 rows selected in 0,016 seconds
00:34:35.811 SQLForm [14:27:37] 0 rows selected in 0,016 seconds||QueryTabControlChange
00:34:35.812 GotoQueryTab done
00:34:35.813 Lock
00:34:35.817 UnLock
 
The logging does indeed not contain a clue. Can you answer the following?
  1. Does the error occur during typing? Or randomly?
  2. If it happens during typing, does it happen while making a text selection?
  3. Is there a specific window type involved (SQL Window, Program Window, ...)?
  4. Did you have multiple PL/SQL Developer instances opened when this happened?
  5. Approximately how long had the PL/SQL Developer instance been running when this happened?
  6. Did you have a Workset opened when this error occurred?
  7. Are you using the version control integration for Git or Subversion?
  8. Can you let us know if the following preference settings were enabled?
    • Oracle / Connection / Check connection
    • Oracle / Connection / Check all Sessions
    • Files / Backup / Save on time interval
  9. Has this happened before in version 14.0 Beta 5 or earlier?
  10. Has this happened before in version 13.0 or earlier?

 
vlevi said:
Stuck again, luckily, I wasn't in any production, I only tried to reproduce the problem, and I succeed.
What did you do to reproduce this?

vlevi said:
Later I added some where clause, and the PL/SQL Developer stopped suddenly :(
Were you typing when it stopped? Did you execute the query when it stopped?
 
Last edited:
Nothing special, I typed, moved the cursor, maybe pressed Ctrl+C, Ctrl-V, I don't know.
I will try again.
The recovery works, I got back the SQL windows before the freezing.

Sorry, but now I was not able to reproduce this.
As you see, the last executed statement is a very simple select * from a table (not view, not synonym), with only a few columns, and about 20 records.

Does the error occur during typing? Or randomly?
Very random. I can use it for hours, and suddenly it happens.
If it happens during typing, does it happen while making a text selection?
Not exactly reproducable.
Is there a specific window type involved (SQL Window, Program Window, ...)?
In an SQL Window
Did you have multiple PL/SQL Developer instances opened when this happened?
No
Approximately how long had the PL/SQL Developer instance been running when this happened?
For the last error, it was only 30 minutes
Did you have a Workset opened when this error occurred?
No
Are you using the version control integration for Git or Subversion?
No
Can you let us know if the following preference settings were enabled?
Oracle / Connection / Check connection
Not checked
Oracle / Connection / Check all Sessions
Not Checked
Files / Backup / Save on time interval
Backup file save in the same directory, 10 minutes interval, save on execute is not checked on

Has this happened before in version 14.0 Beta 5 or earlier?
I don't remember, maybe.
Has this happened before in version 13.0 or earlier?
Never

Support info page :
PL/SQL Developer
Version 14.0.0.1957 Beta (32 bit)
Windows 7 (64-bit) Build 7600 (Actually, it is Windows 10 1909 build)

Physical memory : 8 037 156 kB (2 942 340 available)
Paging file : 12 178 040 kB (2 572 308 available)
Virtual memory : 2 097 024 kB (1 534 784 available)

Parameters
C:\Program Files (x86)\PLSQL Developer 14 Beta\plsqldev.exe
debugsql

Preferences
Session mode: Multi
OCI Library:
Use OCI7: False
Allow Multiple Connections: False

Preference Files
C:\Users\ValentL\AppData\Roaming\PLSQL Developer 14\Preferences\default\Default.ini
C:\Users\ValentL\AppData\Roaming\PLSQL Developer 14\Preferences\valentl\default.ini

Debug file
C:\Users\ValentL\AppData\Roaming\PLSQL Developer 14\PlSqlDev.elf

Plug-Ins
*L-Soft komponensk
 
Last edited:
vlevi said:
Nothing special, I typed, moved the cursor, maybe pressed Ctrl+C, Ctrl-V, I don't know.
I will try again.
The recovery works, I got back the SQL windows before the freezing.

Sorry, but now I was not able to reproduce this.
As you see, the last executed statement is a very simple select * from a table (not view, not synonym), with only a few columns, and about 20 records.
Can you answer the 10 questions above?
 
vlevi said:
While typing, and maybe, when I click with the mosue somewhere in the typed text.
Okay. We want to try to reproduce this, and to maximize the chance for success, we would like to have your preference settings. Can you send the following 2 files to support@allroundautomations.com?

C:\Users\ValentL\AppData\Roaming\PLSQL Developer 14\Preferences\valentl\default.ini

C:\Users\ValentL\AppData\Roaming\PLSQL Developer 14\Preferences\valentl\user.prefs

Thanks in advance!
 
Can you download and install this test version? It will create additional diagnostics.

Beta 7b 32 bit

Beta 7b 64 bit

Run it with the DebugSQL parameter again, and when it freezes, copy the final 100 lines from the debug.txt file in the %APPDAT%\PLSQL Developer 14 directory.
 
You may disregard the 2 posts above. We have reproduced and fixed the issue. We'll release Beta 8 with this fix later today.
 
Back
Top