Maximum execution time of 30 seconds exceeded

[reefland]

Here is the error message:

Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/forum/includes/functions_wysiwyg.php on line 116

Is this another check in addition to the maximum number of characters per post? I currently have that set to 10,000 and when this error came up we were trying to post a very long thread however it only contained 4597 characters without spaces.

Just reading through some other threads on this issue and it was recommended to increase the max time in php however should it really take that long to write 4600 characters?

Thanks for the information xiphoid. Just thanking you here while I edit. :)

Just curious,
Scott Z.

[Floris]

This has been in beta 2 and 3 and now still in 4.

I don't think it is the character length that loops, but the preg_regex that tries to do something with parsing of vb code tags within font tags or the other way around.

I have no problem with mucho text in posts, but when I edit them, and add some fonts and press submit, it b0rks.

You can bypass it by not using the wysiwyg editor. I did receive a lot of lag before the post was finally posted, but it didn't give the above warning.

[Mike Sullivan]

How much formatting did the post have?

Try posting it here in the test forum, with the WYSIWYG editor. If it doesn't work, email me what you were going to post (with formatting, so you'll need to do HTML mail. In this case, Outlook would probably the easiest way to save the formatting)

[reefland]

How much formatting did the post have?

Try posting it here in the test forum, with the WYSIWYG editor. If it doesn't work, email me what you were going to post (with formatting, so you'll need to do HTML mail. In this case, Outlook would probably the easiest way to save the formatting)

I sent it to you via e-mail due to some semi-sensitive information contained. Just FIA the formatting brought the total to 8,271 characters.

Thanks,
Scott Z.

[Mike Sullivan]

Received and it appears to send the WYSIWYG parsing code (mine :)) into an infinite loop of some sorts.

[reefland]

Received and it appears to send the WYSIWYG parsing code (mine :)) into an infinite loop of some sorts.

Is that some sort of bug?

[Scott MacVicar]

indeed it is, Mike will look into it :)

[Floris]

That is what I have been telling you and kier in pm :P

[Mike Sullivan]

That's what you get for PM'ing them. :p

;)

[tomdkat]

One of our users just received this today with 3.0.0 beta 5:

Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/website/includes/functions.php on line 2798

Any ideas on what's going on? I'm sure my problem with functions.php is different than the problem discussed here but is the 30 second timeout related to specific tasks or a more general problem?

Thanks...

Peace...

[tomdkat]

One of our users just received this today with 3.0.0 beta 5:

Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/wSo, it looks like bracketed text inside an unclosed "quote" tag caused our problem:

[ quote ][Test][ /quote ]

works fine, but

[ quote ][Test]

caused our problem. (Of course the spaces are NOT in the real posts...:)).

Peace...

[Mike Sullivan]

Thank you. I will look into that.

[Mike Sullivan]

I could not reproduce this locally nor here.

What's your PHP version?

Also, in includes/functions.php, find this line:

[code]function strip_quotes($text)[/quote] Below it you should see a line that begins with "return preg_replace..." What is the exact code for that line?

[tomdkat]

What's your PHP version?PHP 4.3.2 running as a DSO with Apache 2.0.46 on RedHat Linux 9.


Also, in includes/functions.php, find this line:

function strip_quotes($text) Below it you should see a line that begins with "return preg_replace..." What is the exact code for that line?
Here is the code:


function strip_quotes($text)
{
// threadids that this regex breaks: 74755, 76347
return preg_replace('#\[quote(=("|"|\'|).*\\2)?\]((?>[^\[]*?)|(?R)|.)*\[/quote\]#siU', '', $text);


I'm working on getting a more complete testcase for you. :)

Peace...

[Mike Sullivan]

tomdkat -- someone else actually had the same problem, but I was able to reproduce the issue locally with that version. *shrug*

I've posted a fix to this issue here:
http://www.vbulletin.com/forum/bugs.php?do=view&bugid=499
Let me know if that fixes the problem.

[tomdkat]

tomdkat -- someone else actually had the same problem, but I was able to reproduce the issue locally with that version. *shrug*

I've posted a fix to this issue here:
http://www.vbulletin.com/forum/bugs.php?do=view&bugid=499
Let me know if that fixes the problem.Will do. Thanks!

Peace...

[tomdkat]

tomdkat -- someone else actually had the same problem, but I was able to reproduce the issue locally with that version. *shrug*

I've posted a fix to this issue here:
http://www.vbulletin.com/forum/bugs.php?do=view&bugid=499
Let me know if that fixes the problem.Quick question, in the above thread, you state:
functions.php (twice) and search.php (once) I believe, assuming you made the related bug fixes earlier.
What are the "related bug fixes" you refer to? We're on beta 5 and I'm not sure what other patches need to be applied, if any.

Will there be a beta 6, perhaps?

Thanks...

Peace...

[tomdkat]

Well, that patch seemed to work just fine! Thanks!

Peace...

[tomdkat]

Well one of our users hit this problem again
Fatal error: Maximum execution time of 30 seconds exceeded in /home/pathto/website/includes/functions.php on line 2799
This is what they did:

Clicked "reply" to reply to a topic
Clicked "link" to insert a link
Typed some text and clicked 'Ok'
Typed in the link and clicked 'Ok'
The link appeared in the response box and they clicked "Submit reply" and received the message above

I just tried this myself, and it worked just fine. This user was able to do the above and have it work fine for them too.

So, I'm not sure what else can be done, at this point.

Thanks...

Peace...

[Mike Sullivan]

That's actually a different, although related problem. See the bug fixes posted in these reports: http://www.vbulletin.com/forum/bugs.php?s=&do=list&textsearch=recursive

[Marc Smith]

One of our users just received this today with 3.0.0 beta 5:

Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/website/includes/functions.php on line 2798

Any ideas on what's going on? I'm sure my problem with functions.php is different than the problem discussed here but is the 30 second timeout related to specific tasks or a more general problem?
I've had a couple of folks report this same error on my forums. See post 109 in: http://elsmar.com/Forums/showthread.php?t=6293&page=8&pp=15

I keep seeing a mySQL vsleep issue but haven't correlated the two occurances as simultaneous yet.

[tomdkat]

I've had a couple of folks report this same error on my forums. See post 109 in: http://elsmar.com/Forums/showthread.php?t=6293&page=8&pp=15

I keep seeing a mySQL vsleep issue but haven't correlated the two occurances as simultaneous yet.Thanks...

Peace...

[tomdkat]

At this point, I'm not sure if I should open a NEW bug report or what. Another user has hit this problem again and THIS time I have the "raw" data they were trying to work with.

They posted a message and messed up the "quote" tags. They tried to edit this post to fix the "quote" tags and after pressing "Save changes", they got this error:

Fatal error: Maximum execution time of 30 seconds exceeded in /path/to/website/includes/functions.php on line 2799

Here is the data they were dealing with:
(QUOTE=user)text(/QUOTE)

For what it's worth, from (URL=url)IMDB:(/URL)

(/QUOTE)text(\QUOTE)

I replaced the quare brackets with parentheses. :)

First, we have mis-matched "/quote" tags and even a NEW "\quote" tag . :)

Should I open a new bug report or not?

Peace....

[Scott MacVicar]

just see if it works here.

this forum is using the latest cvs build.

[tomdkat]

just see if it works here.

this forum is using the latest cvs build. (http://www.vbulletin.com/forum/)

[/QUOTE]This is some test text[\quote]

[tomdkat]

Looks like it's working here just fine. We're also running beta 5 but NOT the latest CVS so we can pick up this fix when 3.0.0 is released.

Thanks!

Peace...