Toad World® Forums

Errors that Kill the Beta


#1

I am running 12.7.32, but have been seeing this for a while. I also can’t duplicate the steps to get the error which is why I haven’t reported it before this.

So the problem is that I’ll be working in TOAD and it will freeze up. I think this has mostly been when I’m scrolling in a data grid, sometimes in the editor and sometimes in a Describe window. Then finally the hourglass will show and the entire screen fades. Then an error box will pop up, behind main TOAD window. The only way I can get to it is to use ALt-Ctrl-Del and Switch To. Most of the time there are actually two error windows. Never have I been able to actually read the message on the box - they actually are black windows - no buttons or anything visible. Today I found that I could “Switch To” the one box (it was apparently On Top of the other one, so I couldn’t get to that one) and when I pressed Enter, assuming it would clear the box, it went away. I then tried this for the other box and when I did, TOAD disappeared. I have never been able to recover from these errors - they always result in TOAD being killed.

I wish I could give you more details. In the case today, I had been in several editor windows, each with multiple tabs open, though not as excessive as I sometimes get, used F4 and Ctrl-D to describe a bunch of tables and packages and TOAD had been running since Monday.

Anyway, you should know about this because if others experience it after this version is released, you’ll have some unhappy customers.

Let me know if you need any files to help troubleshoot this.

Blessings,

Phyllis


Phyllis Helton

Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452

phyllis.helton@cru.org


#2

You are several versions behind, you should upgrade. There have been many editor bug fixes, a few affect stability and memory. I’d also recommend deleting Editor*.xml files from your User Files folder. Some of the bugs have affected the values stored within.
I’ve tried to code around them, but to be certain it would be best to sanitize the editor configuration files.

Also, do you use Code Analysis real-time scanning (Options|Code Analysis|General|Check Rules as you type)? If so, a nasty bug was identified the other day that causes Toad to freeze. It’s been resolved for the next beta.

Michael

On 01/28/2015 10:51 AM, phyllis.helton_1150 wrote:

Errors that Kill the Beta

Thread created by phyllis.helton_1150
I am running 12.7.32, but have been seeing this for a while. I also can’t duplicate the steps to get the error which is why I haven’t reported it before this.

So the problem is that I’ll be working in TOAD and it will freeze up. I think this has mostly been when I’m scrolling in a data grid, sometimes in the editor and sometimes in a Describe window. Then finally the hourglass will show and the entire screen
fades. Then an error box will pop up, behind main TOAD window. The only way I can get to it is to use ALt-Ctrl-Del and Switch To. Most of the time there are actually two error windows. Never have I been able to actually read the message on the box - they
actually are black windows - no buttons or anything visible. Today I found that I could “Switch To” the one box (it was apparently On Top of the other one, so I couldn’t get to that one) and when I pressed Enter, assuming it would clear the box, it went away.
I then tried this for the other box and when I did, TOAD disappeared. I have never been able to recover from these errors - they always result in TOAD being killed.

I wish I could give you more details. In the case today, I had been in several editor windows, each with multiple tabs open, though not as excessive as I sometimes get, used F4 and Ctrl-D to describe a bunch of tables and packages and TOAD had been running
since Monday.

Anyway, you should know about this because if others experience it after this version is released, you’ll have some unhappy customers.

Let me know if you need any files to help troubleshoot this.

Blessings,

Phyllis


Phyllis Helton

Data Magician

Digital Strategies, Cru |
Data Sciences & Analytics

Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#3

Yeah. I actually was ready to update my TOAD around the time it failed today.

Glad to know you already identified some bugs. That gives me hope that the ones I’ve hit are fixed.

I do not use the Check Rules as you type option, so at least I’m not dealing with that one.

Is it possible to copy my editor*.xml files from my GA version of TOAD and have them work? I’d rather not recreate my templates, but if I have to, that is a small price to pay for getting rid of those crashes. :slight_smile:

Thanks Michael!

On Wed, Jan 28, 2015 at 11:03 AM, Michael Staszewski bounce-mstaszew@toadworld.com wrote:

Re: Errors that Kill the Beta

Reply by Michael Staszewski
You are several versions behind, you should upgrade. There have been many editor bug fixes, a few affect stability and memory. I’d also recommend deleting Editor*.xml files from your User Files folder. Some of the bugs have affected the values stored within. I’ve tried to code around them, but to be certain it would be best to sanitize the editor configuration files.

Also, do you use Code Analysis real-time scanning (Options|Code Analysis|General|Check Rules as you type)? If so, a nasty bug was identified the other day that causes Toad to freeze. It’s been resolved for the next beta.

Michael

On 01/28/2015 10:51 AM, phyllis.helton_1150 wrote:

Errors that Kill the Beta

Thread created by phyllis.helton_1150
I am running 12.7.32, but have been seeing this for a while. I also can’t duplicate the steps to get the error which is why I haven’t reported it before this.

So the problem is that I’ll be working in TOAD and it will freeze up. I think this has mostly been when I’m scrolling in a data grid, sometimes in the editor and sometimes in a Describe window. Then finally the hourglass will show and the entire screen fades. Then an error box will pop up, behind main TOAD window. The only way I can get to it is to use ALt-Ctrl-Del and Switch To. Most of the time there are actually two error windows. Never have I been able to actually read the message on the box - they actually are black windows - no buttons or anything visible. Today I found that I could “Switch To” the one box (it was apparently On Top of the other one, so I couldn’t get to that one) and when I pressed Enter, assuming it would clear the box, it went away. I then tried this for the other box and when I did, TOAD disappeared. I have never been able to recover from these errors - they always result in TOAD being killed.

I wish I could give you more details. In the case today, I had been in several editor windows, each with multiple tabs open, though not as excessive as I sometimes get, used F4 and Ctrl-D to describe a bunch of tables and packages and TOAD had been running since Monday.

Anyway, you should know about this because if others experience it after this version is released, you’ll have some unhappy customers.

Let me know if you need any files to help troubleshoot this.

Blessings,

Phyllis


Phyllis Helton
Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.


Phyllis Helton

Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452

phyllis.helton@cru.org


#4

Editor*.xml files are all new for this beta. Copy Lexlib.lxl from GA user files to beta and Toad will migrate your templates.

On 01/28/2015 12:25 PM, phyllis.helton_1150 wrote:

Re: Errors that Kill the Beta

Reply by phyllis.helton_1150
Yeah. I actually was ready to update my TOAD around the time it failed today.

Glad to know you already identified some bugs. That gives me hope that the ones I’ve hit are fixed.

I do not use the Check Rules as you type option, so at least I’m not dealing with that one.

Is it possible to copy my editor*.xml files from my GA version of TOAD and have them work? I’d rather not recreate my templates, but if I have to, that is a small price to pay for getting rid of those crashes. :slight_smile:

Thanks Michael!

On Wed, Jan 28, 2015 at 11:03 AM, Michael Staszewski
bounce-mstaszew@toadworld.com wrote:

Re: Errors that Kill the Beta

Reply by Michael Staszewski
You are several versions behind, you should upgrade. There have been many editor bug fixes, a few affect stability and memory. I’d also recommend deleting Editor*.xml files from your User Files folder. Some of the bugs have affected the values stored within.
I’ve tried to code around them, but to be certain it would be best to sanitize the editor configuration files.

Also, do you use Code Analysis real-time scanning (Options|Code Analysis|General|Check Rules as you type)? If so, a nasty bug was identified the other day that causes Toad to freeze. It’s been resolved for the next beta.

Michael

On 01/28/2015 10:51 AM, phyllis.helton_1150 wrote:

Errors that Kill the Beta

Thread created by phyllis.helton_1150
I am running 12.7.32, but have been seeing this for a while. I also can’t duplicate the steps to get the error which is why I haven’t reported it before this.

So the problem is that I’ll be working in TOAD and it will freeze up. I think this has mostly been when I’m scrolling in a data grid, sometimes in the editor and sometimes in a Describe window. Then finally the hourglass will show and the entire screen
fades. Then an error box will pop up, behind main TOAD window. The only way I can get to it is to use ALt-Ctrl-Del and Switch To. Most of the time there are actually two error windows. Never have I been able to actually read the message on the box - they
actually are black windows - no buttons or anything visible. Today I found that I could “Switch To” the one box (it was apparently On Top of the other one, so I couldn’t get to that one) and when I pressed Enter, assuming it would clear the box, it went away.
I then tried this for the other box and when I did, TOAD disappeared. I have never been able to recover from these errors - they always result in TOAD being killed.

I wish I could give you more details. In the case today, I had been in several editor windows, each with multiple tabs open, though not as excessive as I sometimes get, used F4 and Ctrl-D to describe a bunch of tables and packages and TOAD had been running
since Monday.

Anyway, you should know about this because if others experience it after this version is released, you’ll have some unhappy customers.

Let me know if you need any files to help troubleshoot this.

Blessings,

Phyllis


Phyllis Helton

Data Magician

Digital Strategies, Cru |
Data Sciences & Analytics

Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


Phyllis Helton

Data Magician

Digital Strategies, Cru |
Data Sciences & Analytics

Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#5

Wonderful! Thanks Michael.

On Wed, Jan 28, 2015 at 12:28 PM, Michael Staszewski bounce-mstaszew@toadworld.com wrote:

Re: Errors that Kill the Beta

Reply by Michael Staszewski
Editor*.xml files are all new for this beta. Copy Lexlib.lxl from GA user files to beta and Toad will migrate your templates.

On 01/28/2015 12:25 PM, phyllis.helton_1150 wrote:

Re: Errors that Kill the Beta

Reply by phyllis.helton_1150
Yeah. I actually was ready to update my TOAD around the time it failed today.

Glad to know you already identified some bugs. That gives me hope that the ones I’ve hit are fixed.

I do not use the Check Rules as you type option, so at least I’m not dealing with that one.

Is it possible to copy my editor*.xml files from my GA version of TOAD and have them work? I’d rather not recreate my templates, but if I have to, that is a small price to pay for getting rid of those crashes. :slight_smile:

Thanks Michael!

On Wed, Jan 28, 2015 at 11:03 AM, Michael Staszewski bounce-mstaszew@toadworld.com wrote:

Re: Errors that Kill the Beta

Reply by Michael Staszewski
You are several versions behind, you should upgrade. There have been many editor bug fixes, a few affect stability and memory. I’d also recommend deleting Editor*.xml files from your User Files folder. Some of the bugs have affected the values stored within. I’ve tried to code around them, but to be certain it would be best to sanitize the editor configuration files.

Also, do you use Code Analysis real-time scanning (Options|Code Analysis|General|Check Rules as you type)? If so, a nasty bug was identified the other day that causes Toad to freeze. It’s been resolved for the next beta.

Michael

On 01/28/2015 10:51 AM, phyllis.helton_1150 wrote:

Errors that Kill the Beta

Thread created by phyllis.helton_1150
I am running 12.7.32, but have been seeing this for a while. I also can’t duplicate the steps to get the error which is why I haven’t reported it before this.

So the problem is that I’ll be working in TOAD and it will freeze up. I think this has mostly been when I’m scrolling in a data grid, sometimes in the editor and sometimes in a Describe window. Then finally the hourglass will show and the entire screen fades. Then an error box will pop up, behind main TOAD window. The only way I can get to it is to use ALt-Ctrl-Del and Switch To. Most of the time there are actually two error windows. Never have I been able to actually read the message on the box - they actually are black windows - no buttons or anything visible. Today I found that I could “Switch To” the one box (it was apparently On Top of the other one, so I couldn’t get to that one) and when I pressed Enter, assuming it would clear the box, it went away. I then tried this for the other box and when I did, TOAD disappeared. I have never been able to recover from these errors - they always result in TOAD being killed.

I wish I could give you more details. In the case today, I had been in several editor windows, each with multiple tabs open, though not as excessive as I sometimes get, used F4 and Ctrl-D to describe a bunch of tables and packages and TOAD had been running since Monday.

Anyway, you should know about this because if others experience it after this version is released, you’ll have some unhappy customers.

Let me know if you need any files to help troubleshoot this.

Blessings,

Phyllis


Phyllis Helton
Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.


Phyllis Helton
Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452
phyllis.helton@cru.org

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag this post as spam/abuse.


Phyllis Helton

Data Magician
Digital Strategies, Cru | Data Sciences & Analytics
Office :phone: 407-515-4452

phyllis.helton@cru.org