[9.5.449 Pro] - Very strange bug?

[9.5.449 Pro] - Very strange bug?

I've run into a very strange bug/event. I have got a table in Oracle that causes SQL Editor to crash in case a certain combination of columns is selected from it. There are a bunch of NUMBERs, VARCHAR2s, 3 CLOBs, and 2 TIMESTAMPs. The rest of the columns seem not to make any difference but as soon as all the CLOBs and the TIMESTAMPs are selected SE goes down in flames. Check this short video here.

The CREATE statement of the table (extracted by Oracle SQL Developer):

Code:

CREATE TABLE "DEMO1"."SYM_TRIGGER_HIST"
( "TRIGGER_HIST_ID" NUMBER(22,0) NOT NULL ENABLE,
"TRIGGER_ID" VARCHAR2(128 BYTE) NOT NULL ENABLE,
"SOURCE_TABLE_NAME" VARCHAR2(255 BYTE) NOT NULL ENABLE,
"SOURCE_CATALOG_NAME" VARCHAR2(255 BYTE),
"SOURCE_SCHEMA_NAME" VARCHAR2(255 BYTE),
"NAME_FOR_UPDATE_TRIGGER" VARCHAR2(255 BYTE),
"NAME_FOR_INSERT_TRIGGER" VARCHAR2(255 BYTE),
"NAME_FOR_DELETE_TRIGGER" VARCHAR2(255 BYTE),
"TABLE_HASH" NUMBER(38,0) DEFAULT 0 NOT NULL ENABLE,
"TRIGGER_ROW_HASH" NUMBER(38,0) DEFAULT 0 NOT NULL ENABLE,
"TRIGGER_TEMPLATE_HASH" NUMBER(38,0) DEFAULT 0 NOT NULL ENABLE,
"COLUMN_NAMES" CLOB NOT NULL ENABLE,
"PK_COLUMN_NAMES" CLOB NOT NULL ENABLE,
"LAST_TRIGGER_BUILD_REASON" CHAR(1 BYTE) NOT NULL ENABLE,
"ERROR_MESSAGE" CLOB,
"CREATE_TIME" TIMESTAMP (6) NOT NULL ENABLE,
"INACTIVE_TIME" TIMESTAMP (6),
CONSTRAINT "SYM_TRIGGER_HIST_PK" PRIMARY KEY ("TRIGGER_HIST_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "DEMO" ENABLE
) SEGMENT CREATION IMMEDIATE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "DEMO" NO INMEMORY
LOB ("COLUMN_NAMES") STORE AS SECUREFILE (
TABLESPACE "DEMO" ENABLE STORAGE IN ROW CHUNK 8192
NOCACHE LOGGING NOCOMPRESS KEEP_DUPLICATES
STORAGE(INITIAL 106496 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
LOB ("PK_COLUMN_NAMES") STORE AS SECUREFILE (
TABLESPACE "DEMO" ENABLE STORAGE IN ROW CHUNK 8192
NOCACHE LOGGING NOCOMPRESS KEEP_DUPLICATES
STORAGE(INITIAL 106496 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
LOB ("ERROR_MESSAGE") STORE AS SECUREFILE (
TABLESPACE "DEMO" ENABLE STORAGE IN ROW CHUNK 8192
NOCACHE LOGGING NOCOMPRESS KEEP_DUPLICATES
STORAGE(INITIAL 106496 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)) ;

CREATE INDEX "DEMO1"."SYM_IDX_TRIGG_HIST_1" ON "DEMO1"."SYM_TRIGGER_HIST" ("TRIGGER_ID", "INACTIVE_TIME")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "DEMO" ;

Thank you very much for reporting this. We are able to reproduce this issue and investigating the root cause.

PS. An exception occurs in oracore12.dll OCI library when a certain combination of CLOB and TIMESTAMP columns referenced in the SELECT list

That's pretty bad. Is there anything there that can be done about it besides not selecting certain combinations of columns?

Let me get back to this when I hear from the team, we are still investigating if it's caused by an issue on our end.