Print Thread
Find a ( in a procedure cause PL to hang
#59760 03/12/19 06:33 PM
Joined: Oct 2002
Posts: 59
Quebec,Canada
D
DLGL Offline OP
Member
OP Offline
Member
D
Joined: Oct 2002
Posts: 59
Quebec,Canada
Hi,

I don't know if it was reported ?

If you try to find an open parenthesis ( in a procedure PL seems to hang, was not patient enough to wait ;-)

Using version 13.0.2.1898 64 bits.

Same test in version 13.0.1 works ok.

Thanks !


Last edited by DLGL; 03/12/19 06:33 PM.
Re: Find a ( in a procedure cause PL to hang
DLGL #59764 03/13/19 09:53 AM
Joined: Aug 1999
Posts: 22,208
Member
Offline
Member
Joined: Aug 1999
Posts: 22,208
It seems to work fine for me. Are there any special conditions in the editor text or search options?


Marco Kalter
Allround Automations
Re: Find a ( in a procedure cause PL to hang
Marco Kalter #59768 03/13/19 01:01 PM
Joined: Oct 2002
Posts: 59
Quebec,Canada
D
DLGL Offline OP
Member
OP Offline
Member
D
Joined: Oct 2002
Posts: 59
Quebec,Canada
Hi Marco,

I found that Regular Expression was on ! When off everything is okay.

If you turn on Regular Expression and the procedure has around 10 lines, it is going ta take a long time. But it will eventually come back.

The procedure I was editing is around 1000 lines.

Is it normal to take so much time using regular expression ?
Searching a normal word ex: BEGIN is fast.

Same with 13.01.

Thank you !

Re: Find a ( in a procedure cause PL to hang
DLGL #59775 03/14/19 10:19 AM
Joined: Aug 1999
Posts: 22,208
Member
Offline
Member
Joined: Aug 1999
Posts: 22,208
This should not take that long. We'll investigate.


Marco Kalter
Allround Automations
Re: Find a ( in a procedure cause PL to hang
Marco Kalter #59781 03/14/19 01:08 PM
Joined: Oct 2002
Posts: 59
Quebec,Canada
D
DLGL Offline OP
Member
OP Offline
Member
D
Joined: Oct 2002
Posts: 59
Quebec,Canada
Thank you ! :-)

Re: Find a ( in a procedure cause PL to hang
DLGL #62657 07/27/21 02:11 PM
Joined: Sep 2003
Posts: 387
London, UK
Member
Offline
Member
Joined: Sep 2003
Posts: 387
London, UK
I hit this every time I accidentally leave an unescaped and unmatched bracket in a Regular Expression search, e.g.
Code
nvl(\w+\.version_no
when what I meant to search for was
Code
nvl\(\w+\.version_no
Instead of reporting it immediately as an invalid regex (as for example Notepad++ or Oracle regexp_ functions would do), it hangs for ages. This still happens in 14.0.6.

And if you are revisiting REs, it would be super handy if we didn't have to escape the space character (again, similarly to Notepad++ and Oracle regexp_ functions).


Moderated by  support 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.1.33 Page Time: 0.210s Queries: 15 (0.124s) Memory: 2.5164 MB (Peak: 3.0380 MB) Data Comp: Off Server Time: 2024-05-03 07:38:09 UTC
Valid HTML 5 and Valid CSS