Oracle bug? ORA-07445, pl/SQL for in ()

My process is as follows:

Create or replace package body proc_body
Procedure init (start_date date, end_date date) is
For rec in (here is a query associated with several tables [R query]) loop
......
End loop;
End;
End proc_body;

I have created several processes for initializing data and running them directly in pl/SQL dev without responding, checking the running SQL, without any information about the process. Re-execute this process in sqlplus and directly disconnect from the Oracle server (reporting end of... communication)
 
These processes pass the test in the test environment. There is no problem, but they cannot be executed in the production environment. view the oracle alert Log, each time a task is run, an error like the following occurs:
170 ORA-07445: exception: core dump [0000000100405A00] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
-------------------------------------------------------
173 ORA-07445: exception: core dump [0000000101C63D14] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFFB33F03F8] [] []
---------------------------------------------------------
174 ORA-07445: exception: core dump [0000000100405A00] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
--------------------------------------------------------
177 ORA-07445: exception: core dump [0000000101C63D14] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFFB33F03F8] [] []
----------------------------------------------------------------
178 ORA-07445: exception: core dump [0000000101C63D14] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFFB33F03F8] [] []
 
Dba said that the 07445 error is hard to solve. directly run the R query in advance and insert it into a table (create table txx as R query ). The process becomes like this:

Create or replace package body proc_body
Procedure init is
For rec in (select * from txx) loop
......
End loop;
End;
End proc_body;

Then run the process. The process runs successfully and data Initialization is complete. This process does not involve any remote operations. In the end, this is the solution.

But there is no problem in deploying jobs for the same type of process.