"Ask David Mullen Anything" thread problem

[Clint Lealos]

Everytime I click on that thread I get this message:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 19964 bytes) in /home/reduser/public_html/forum/showthread.php on line 1275

Is this something I am doing wrong on my end? Can I fix it, or is this on Reduser's side of things? Sorry if this question is a dumb one. I'm ignorant.

Thanks

 

[Clint Lealos]

I bet David would know how to fix this

 

[Jeff Kilgroe]

Not seeing this problem here... ?

You might need to clear your history and dump your browser cache. Something could be clogged up.

 

[Clint Lealos]

Thanks Jeff. I signed out and signed back in and the problem is gone...for now. Its not the first time I have gotten that error message. Maybe if I signed out from Reduser every once and a while I wouldn't have this problem

 

[Keith Nealy]

I've had this same problem "forever." can't seem to get in. Emails to RED about it get no answer. Logged out then back in- no difference.
Very frustrating as it was my favorite thread.

Keith

 

[Peter Moretti]

No problem here. It's got be something rather specific to certain computers. (I'm running XP 32 bit and IE 8.)

 

[Jeff Kilgroe]

Has to be something with individual computers/accounts that I can't see or duplicate on my end. I don't have admin privileges to look at code or database issues, server-side issues, etc.. That's Jason Ramsey's department.

I have experienced database errors myself on the forums if I regularly open up forum threads in new pages/tabs and then go back to other pages I clicked on a while back. Especially if I don't log-out and do it a bunch over a day or two.

 

[Conrad Hunziker]

Actually, no. Thats a specific server error message, not related to visitors computers or browsers. It may be a specific page in Davids thread thats doing it, or it may be the defaults that the visitor has on this forum combined with that thread/page.

But specifically, PHP is trying to allocate more memory to process & render a page, and there is a server setting that is preventing it from allocating more memory. There is a limit on purpose, so that a runaway PHP script cant take down the entire server (either by error or malicious activity)

To fix this error, the server admin must either:
- increase the memory_limit in the php.ini file
- add/edit the php_value memory_limit xxM in the .htaccess file
- alter the visitor preferences to try and bring the memory required to process that page in line.

If the admin elects the first two, then the server (apache?) must be restarted. The user could also adjust his settings in the forums to view threads using the forum default, which may be the setting he has that is causing this error.

 

[Pietro Impagliazzo]

Weird, since I view 40 posts per page and have no problems viewing the thread.

I'm on Chrome, Windows 7.

 

[Jeff Kilgroe]

Actually, no. Thats a specific server error message, not related to visitors computers or browsers. It may be a specific page in Davids thread thats doing it, or it may be the defaults that the visitor has on this forum combined with that thread/page.

Yes, it is a server-side error, but that still doesn't mean it's user-triggered. The database errors I mentioned above are all server-side errors as well and even though they are SQL errors in most situations, are actually triggered by vBulletin's own sloppy session tracking. I've seen PHP errors related to the same.

you are correct, it could be related to specific settings that these users may have in relation to the forum. But there's not a whole lot of options there. There's only two styles to choose from and selectable posts per page of 10, 20 30 or 40. I keep mine on 40 posts/page, no problems here. I've been through every page of the thread and can't duplicate the problem. People logging out and logging back in with that fixing the problem seems indicative of a user-triggered error.

Anyway, we're doing nothing more than academic speculation here. Jason is the admin and needs to review server logs. Depending on what logging he has enabled and available. Perhaps he can see if he can identify a usage pattern or specific user request or condition that triggers them.

 

[Clint Lealos]

Hey guys, thanks for all the info. This stuff is a bit over my head. I can tell you that I also have my preferences set at 40 posts per page, and I am pretty much always signed in to Reduser. Once I signed out, I checked the problem thread again and it worked. I signed back in and it still works My best guess is that is because I almost never sign out. Anyway, thanks again.