Database errors being reported since upgrade to 4.2.0

[Zachery]

Its directly related to the size and complexity of threads, using threaded and hybrid view consumes more memory.

[ZombieAndy]

Ok guys ive increased it to 48 and tried again, the error does not occure while this is disabled but as soon as i enabled it again..

Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 41680878 bytes) in /removed/includes/functions_threadedmode.php on line 23

[ZombieAndy]

It was 8 initially, i increased it to 18 (and again to 30) myself to see if i could get around this error that way but the error continues just in larger numbers.

I Could keep increasing the memory but i dont see why a single script would need so much when it never has before?

[Zachery]

Nothing should have changed on our end regarding those sorts of threads. Chances are it is a change your webhost made, and it coincided with your vBulletin 4 uprade.

your webhost has set an 18mb limit on php memory, which is fairly small.

We'd recommend at least 32mb of memory. Be aware though that these mods are depreciated and not highly supported. They also typically take more resources.

[acwatts]

I keep getting a square checkered box flashing up then disappearing when scrolling through your threads on your forum, is that supposed to happen.

[ZombieAndy]

You can re-enable it, but you'll need more memory to deal with larger threads.

OK so why has this only happened since we upgraded to 4.2? we'd never seen this error before then so my question is really, whats changed to cause this and how do i fix that?

[Zachery]

You can re-enable it, but you'll need more memory to deal with larger threads.

[ZombieAndy]

I Still dont really see what your getting at, no i havnt had any more reports of this error since disabling threaded view but i am being asked already when its being switched back on, i cant just permanently disable it. Its popular on my forums.

It dosnt seem to only effecting large threads either, ive seen it reported in threads with only 3 or 4 replies, this has also been only occuring since i updated our forum software to 4.2 so has the way that data is compiled for the threaded view been changed at all? if so can you give me an alternative or can i use the old functions_threadedmode.php file again?

[Zachery]

That isn't a database error. Other methods of viewing threads, like threaded and hybrid mode can consume large amounts of memory to display the data in that format. Which is why they asked you to disable it.

Are you still getting php out of memory errors since disabling threaded mode?

[ZombieAndy]

Ive disabled threaded view for now and am monitoring it but to be honest im not sure what you guys are trying to prove?

Whats this error you think it might be and how do i resolve?

[Hartmut]

Are very large threads affected by this error?

That's why I called for threaded mode as I believe that this might be the error.

[Dominic]

Are very large threads affected by this error?

[Hartmut]

That's how I could see if that is the problem which I was thinking of. Just give it a try, you can enable it afterwards as I just want to see if the error is gone then

[ZombieAndy]

Seems to be multiple threads rather than just 1 in particullar and i think it would cause abit of a backlash if i disabled threaded mode, alot of my members seem to prefer it.

[Hartmut]

I've had a look at the code in the file you quoted, but can't imagine why you get such an error. What you could try is to disable the threaded mode or simply split the thread which causes this error. Then keep an eye on it if the error still appears...???