Memory Exception on Closure of POP-UP Viewer of CLOB

Toad for Oracle
1

If you open up two editor windows each with its own connection. On connection number 1 describe a table with a CLOB. Leaving the describe pop-up window open, change windows to the second editor using the 2nd connection and run a SELECT query. With the describe pop-up, open a Pop-Up on the CLOB information, update the data, commit, then close the clob pop-up, then close the table describe.

TOAD throws a memory violation as can be seen below. unfortunately, once this occurs, it becomes impossible to describe any future tables on any windows/tabs within toad. It throws the error “A component named F4HolderForm already exists”.

If this could get fixed, it would be greatly appreciated.

Thanks,

David

EurekaLog 7.5.1.0

Application:

1.1 Start Date : Fri, 9 Feb 2018 09:01:57 -0600
1.2 Name/Description: Toad.exe - (Toad® for Oracle)
1.3 Version Number : 12.12.0.39
1.4 Parameters :
1.6 Up Time : 16 minute(s), 1 second(s)

Exception:

2.1 Date : Fri, 9 Feb 2018 09:17:59 -0600
2.2 Address : 0000000009AC9DC5
2.3 Module Name: Toad.exe - (Toad® for Oracle)
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 0000000009AC9DC5 in module ‘Toad.exe’. Read of address 0000000000000070.
2.7 ID : 2A120000
2.8 Count : 1
2.11 Sent : 0

User:

3.2 Name: David

Active Controls:

4.1 Form Class : TfrmMain
4.2 Form Text : Toad for Oracle - [EAI_BDEV@EAIBD - Editor (New 4 *)]
4.3 Control Class: TtdDScintilla
4.4 Control Text : insert into T_EAI_TEST_CASE
(CASE_ID, CASE_NM, CASE_DS, APPL_CD, ACTV_INACT_IN)
values
(
(select NVL(max(case_id),0)+ 1 from t_eai_test_case),
‘MSO:_RRD:_Future Dt, Success’,
‘MSO:_RRD:_Future Dt, Success’,
18,
‘A’
);
commit;
.
insert into t_eai_test_case_scenario
select CASE_SCENARIO_ID + rownum, CASE_ID, ORD_NO, CASE_SCENARIO_NM, CASE_SCNEARIO_DS, CASE_CONFIG_ID, MSG_HDR_TX, MSG_BODY_TX, EXEC_SQL_TX, EXEC_TIMEOUT_DUR_NO, VAL_SUCCESS_FAIL_IN, VAL_SUCCESS_FAIL_TS, VAL_01_DS, VAL_SQL_01_TX, VAL_EXPECTED_RSLT_01_TX, VAL_ACTUAL_RSLT_01_TX, VAL_SUCCESS_FAIL_01_IN, VAL_02_DS, VAL_SQL_02_TX, VAL_EXPECTED_RSLT_02_TX, VAL_ACTUAL_RSLT_02_TX, VAL_SUCCESS_FAIL_02_IN, VAL_03_DS, VAL_SQL_03_TX, VAL_EXPECTED_RSLT_03_TX, VAL_ACTUAL_RSLT_03_TX, VAL_SUCCESS_FAIL_03_IN, VAL_04_DS, VAL_SQL_04_TX, VAL_EXPECTED_RSLT_04_TX, VAL_ACTUAL_RSLT_04_TX, VAL_SUCCESS_FAIL_04_IN, CREATE_TS, CREATE_USER_NM, LAST_UPDT_TS, LAST_UPDT_USER_NM, EXEC_SQL_CMPLT_TS, EXEC_SQL_CMPLT_TX, CASE_CONFIG_CMPLT_TS, CASE_CONFIG_CMPLT_TX, VAL_ACTU

Computer:

5.2 Total Memory : 25760448512 (23.99 Gb)
5.3 Free Memory : 18993696768 (17.69 Gb)
5.4 Total Disk : 1024099086336 (953.77 Gb)
5.5 Free Disk : 257480876032 (239.80 Gb)
5.6 System Up Time : 1 day(s), 22 hour(s), 43 minute(s), 47 second(s)
5.7 Processor : Intel® Core™ i7 CPU 980 @ 3.33GHz
5.8 Display Mode : \.\DISPLAY1[PRIMARY]: 1920x1080x32 96 DPI @ 0x0, \.\DISPLAY2: 1920x1080x32 96 DPI @ -1920x-13
5.9 Display DPI : 96
5.10 Video Card : NVIDIA GeForce GTX 970 (driver 23.21.13.8813 - RAM 4293918720)
5.11 Printer : HP Officejet 6600 (driver 6.1.7601.17514)
5.12 Virtual Machine:

Operating System:

6.1 Type : Microsoft Windows 7 (64 bit)
6.2 Build # : 7601 (6.1.7601.18015)
6.4 Non-Unicode Language: English (0409)
6.5 Charset/ACP : 0/1252
6.6 Install Language : English (0409)
6.7 UI Language : English (0409)

Steps to reproduce:

8.1 Text:

Call Stack Information:

|Methods |Details|Stack |Address |Module |Offset |Unit |Class |Procedure/Method |Line |

|*Exception Thread: ID=13148; Parent=0; Priority=-2 |
|Class=; Name=MAIN |
|DeadLock=0; Wait Chain= |

Comment=
7FFFFFFE
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
00000040
2

Under Options -> Data Grids -> Data, do you have either “Preview CLOB and LONG data” or “Deferred Lob read” checked?

Probably best to leave both unchecked, although I wasn’t able to reproduce this even after playing with those options.

Can you reproduce this consistently?

3

Yes, I can produce this consistently. I responded over the weekend, but don’t see my response on the site. Here are the steps again:

  1.  Open TOAD using User1@DB1. Editor window should be open.

  2.  Using Object Browser, select table with CLOB and press F4 to “describe” the table in a POP-UP.

  3.  Click on Data tab

  4.  Open second Editor window.

  5.  Change connections to User2@DB2

  6.  Run SELECT statement to populate GRID.  Doesn’t matter if this contains a clob or not.

  7.  Update existing CLOB data on the “describe” POP-UP using User1@DB1.  COMMIT.

  8.  Close Window and failure will occur.

Thanks,

David

From: John Dorlon [mailto:bounce-jdorlon@toadworld.com]

Sent: Friday, February 09, 2018 10:23 AM

To: toadoracle@toadworld.com

Subject: [External Email] RE: [Toad for Oracle - Discussion Forum] Memory Exception on Closure of POP-UP Viewer of CLOB

EXTERNAL EMAIL

RE: Memory Exception on Closure of POP-UP Viewer of CLOB

Reply by John Dorlon

Under Options -> Data Grids -> Data, do you have either “Preview CLOB and LONG data” or “Deferred Lob read” checked?

Probably best to leave both unchecked, although I wasn’t able to reproduce this even after playing with those options.

Can you reproduce this consistently?

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle Forum notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.

***** This email is from an external sender outside of the CenterPoint Energy network. Be cautious about clicking links or opening attachments from unknown sources. *****

4

Hi David,

Unfortunately, I’m still not able to reproduce this. I see you are using a 11g client - I tried with that but it didn’t make any difference.

WIll you zip up and send me your user files folder? You can send it to john.dorlon@quest.com. Maybe there is some option at play here.

-John

5

David and I talked offline.

In case anyone is watching this thread:

Shortened steps to reproduce this are:

  1. Have the “Execute queries in threads” option checked.
  2. Just make one connection.
  3. Go to Schema Browser, Data tab.
  4. Double-click a Clob cell. Make an edit and post.
  5. Close the clob editor.
  6. Close the Schema Browser.
    To avoid the error, uncheck the “Execute queries in threads” option

Fixed for next beta.