When I run a Rails console and access a new model (triggers a describe) there's a high chance that the operation will lock up the console. My CPU usage shoots up like it's stuck in a tight loop somewhere.
Here is a stack trace and sample output from the process during a freeze.
This only happens in development with a Rails console. If I run a Rails server or run ActiveJob I'm not getting any problems. I tried upgrading versions of instant client and that also did not help. I imagine this isn't impacting a lot of people but I can reproduce this reliably.
I also opened an issue with Oracle Enhanced but after looking at the stack traces it seems to happen in oci8_do_describe which means it might be more with this repo than theirs.
When I run a Rails console and access a new model (triggers a describe) there's a high chance that the operation will lock up the console. My CPU usage shoots up like it's stuck in a tight loop somewhere.
Here is a stack trace and sample output from the process during a freeze.
This only happens in development with a Rails console. If I run a Rails server or run ActiveJob I'm not getting any problems. I tried upgrading versions of instant client and that also did not help. I imagine this isn't impacting a lot of people but I can reproduce this reliably.
I also opened an issue with Oracle Enhanced but after looking at the stack traces it seems to happen in
oci8_do_describewhich means it might be more with this repo than theirs.Ruby version: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
Oracle Database version: 11g
Rails version: 5.1.6.1
Ruby OCI8 version: 2.2.4.1