Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

Welcome to BZPower!

Hi there, while we hope you enjoy browsing through the site, there's a lot more you can do if you register. The process is easy and you can use your Google, Facebook, or Twitter account to make it even faster. Some perks of joining include:
  • Create your own topics, participate in existing discussions, and vote in polls
  • Show off your creations, stories, art, music, and movies and play member and staff-run games
  • Enter contests to win free LEGO sets and other prizes, and vote to decide the winners
  • Participate in raffles, including exclusive raffles for new members, and win free LEGO sets
  • Send private messages to other members
  • Organize with other members to attend or send your MOCs to LEGO fan events all over the world
  • Much, much more!
Enjoy your visit!

Posted Image


Issue Information

  • #000069

  • Issue

Issue Confirmations

  • Yes (7)No (0)
Locked 
Photo

Fatal Error Opening Blog?

Posted by An/A Blade on Nov 29 2012 - 04:27 PM

Alright; so this is an odder error. This popped up, when I was browsing the blogs, specifically opening this blog; I'll put it into code tags just in case.
[b]Fatal error[/b]: Maximum execution time of 30 seconds exceeded in [b]/home/bzpower/public_html/board/ips_files/sources/classes/text/parser.php[/b] on line [b]583[/b]
I have never seen this before the recent upgrade, and the fact that it's currently happened four times when I open that specific blog(And seemingly only that blog), is a very curious thing. And just to confirm; all the blogs on the first page open correctly, except for the blog I linked, which is Jean Valjean's blog, which refuses to open, citing that error.

/EDIT: More interesting: There's actually different error codes for the other two tries: One calls 'line 1061', and the other calls 'line 1058'. The first two tries called the same line, however.

//EDIT: Further updates; one of my tries to make sure it was still happening managed to call a different error, in '/home/bzpower/public_html/board/ips_files/sources/base/core.php on line 5387'

:kaukau: I have documented the same problem, naturally.  At first I was wondering if you were talking about me, and then I saw you mention my name later on, which was helpful.  I'm not sure why it affects just one blog in particular, and I've gone through some of the same experiments that you have and opened another ticket.  Even though it looks like you beat me to it, I noticed several other issues that have come up and documented those as well.  Hopefully this and the other issues get solves soon.  Meanwhile, I will remove the section in my ticket dealing with this problem, edit it out, and edit it back into this post here for further information.
 
EDIT:
 
Whenever I try to look at my own blog, I get this message:
 
 

 
 


Fatal error: Maximum execution time of 30 seconds exceeded in /home/bzpower/public_html/board/ips_files/sources/classes/text/parser.php on line 1058

 

 
When I asked a friend to look at my bog, he came across the same problem.  We are capable at looking at the blogs of other people, but not mine.


24601


Edited by Jean Valjean, Nov 29 2012 - 05:01 PM.


I think it is a general blog problem - I can't get into the Bones Blog Archive. Oddly, I can view the front page of the blog, but not the archive. 
 
Fatal error: Maximum execution time of 30 seconds exceeded in /home/bzpower/public_html/board/ips_files/sources/classes/text/parser.php on line 1061
 
Fatal error: Maximum execution time of 30 seconds exceeded in /home/bzpower/public_html/board/ips_files/sources/classes/text/parser.php on line 583
 
Looks like someone needs to look at parser.php, lines 583, 1061, and 1058.

base/core.php has errors as well; but I only saw it the once.

However, it's odd, because I can even get into my own blog, and it's old pages, without any problems... What could be in those php files that is causing these problems?

I can view most of the blogs, but Valjean's gave me the dreaded fatal error. None of the other blogs (at least, on the first page) gave me the error. I appear to be able to go to any page of any blog I can get to, but I cannot edit a content block or create a new entry.
 
Ah, Invision. You're just so good at blogs.
 
EDIT: I appear to be able to create entries now without getting an error.

Edited by Sumiki, Nov 29 2012 - 06:37 PM.


I've logged a support ticket with Invision for this.

:kaukau: I just got this fatal error while trying to look through some of the older pages of the Bones Blog.  This is the first sign I've got that it's affecting more than one blog.  Coincidentally, we both happen to have bucketloads of text (although mine's mostly saved as drafts), which might have something to do with it.  I'm not sure.
 

24601



Can you guys provide additional links that are causing this? Invision needs some more data points to get to teh root of the issue.

Thanks!

Here's a link from a page on Bones' blog which has the error.

Page 16, for the record; though I haven't seen any others that mess up like that so far.

This link to the Bones Blog Archive, page 5
 
This link to the Bones blog Archive, page 1
 
These two links caused the error messages in my post above.

Edited by fishers64, Nov 30 2012 - 06:27 PM.


Knowing next to nothing about how the back end of the site works, could it have anything to do with entries on those pages having a large number of replies? I know the first page of Kraggh's blog has had that ongoing "versus" entry that, due to how he re-edits it to start a new discussion topic, has accumulated a massive number of replies. Do the offending pages on the Bones Blog also have entries with lots of replies? Could that be what's causing it?

Knowing next to nothing about how the back end of the site works, could it have anything to do with entries on those pages having a large number of replies? I know the first page of Kraggh's blog has had that ongoing "versus" entry that, due to how he re-edits it to start a new discussion topic, has accumulated a massive number of replies. Do the offending pages on the Bones Blog also have entries with lots of replies? Could that be what's causing it?

 
I doubt it. The things I linked to were archive pages that just made a list of entry titles. 

Okay, so the problem has been resolved in the short term. Quick summary is:
  • Invision changed the way they parse content with this release.
  • Parsing includes processing BBCode, emoticons, and the badword filter.
  • Topics and posts have their content parsed and cached upon creation, while blog entries do not. They're parsed every time they're accessed.
  • Those two blogs, on those particular views, had a large amount of text, so the parser has a lot of work to do when they're loaded.
  • In particular, the large amount of emoticons and entries in the badword filter made the parser time out when those two blogs were loaded.
  • The quick fix has been to reduce the number of blog entries that are displayed per page - the default is now 5 and users can customize up to 10.
  • Invision will change the behavior in the next release so that it caches the parsed content like in topics.
  • The administration will start to reduce the number of entries in the badword filter to help reduce the strain on the parser. This does NOT mean a complete revamp. There are, however, lots of links that are now dead that can be removed.
Please let me know if you still see the 'Fatal Error' anywhere.

The links I provided still produce the error. I suppose it is not too big of a deal, but it sure is annoying, especially on blogs with a long history.

Thanks, I'll see if there's anything that can be done here.

fishers' links should work now, but it's more of a hack than a fix. I'm going to defer this as the root of the issue will be resolved in a future release.


-Windrider-
Oct 18 2014 07:45 PM

Blade has offered that this issue hasn't popped up recently, so after about two years, we'll call this one closed.



locked issue





2 user(s) are reading this issue

1 members, 1 guests, 0 anonymous users


Aanchir