Fatal error: Allowed memory size

[Zachariah]

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 270884 bytes) in /www/vbulletin.org/htdocs/forum/search.php on line 980

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 1024 bytes) in /www/vbulletin.org/htdocs/forum/includes/functions.php on line 496

[nexialys]

forget the search engine, this is a crap... (and NO, this is not the original from vB... it was hacked to hell)

[Zachariah]

What are you talking about ? :confused:

- I did a search just now here @ vb.org and got this error so I posted it.

[Brad]

forget the search engine, this is a crap... (and NO, this is not the original from vB... it was hacked to hell)

There are *small* modifications made to it but for the most part it's the same code that came with 3.0.x by default. We've simply outgrown the default method of searching (vB building the search index by itself).

The script throws this error simply because it runs out of memory (a php limit, the memory is there hardware wise but php can only use so much of it at any given time). When we upgrade it'll be fixed, for now you should try using less common terms in your search queries and only search a limited number of forums instead of the entire board in one shot.

[Andreas]

naxialys, this is a problem with vBulletin built-in search, not a problem with vBorg code.
I've had this on my board since over 1 year, I pseudo-fixed it by adding memory_get_usage and spit out an error ("too many results blah") when it was going too high.

Only solution is to use Fulltext.

[Zachariah]

Btw:
My search was on.

- vB3.5 Modifications and all Subs only
- Ill drop it down to 2-3 forums @ a time.

[Paul M]

If the upgrade to 3.5 is not going to be soon then why not turn on fulltext searching - it is available in later 3.0 versions as well isn't it ?

[nexialys]

If the upgrade to 3.5 is not going to be soon then why not turn on fulltext searching - it is available in later 3.0 versions as well isn't it ?turning to full search would mean a complete re-index of the database... would take at least hours if not a day with the stuff we have here...

and the fulltext of 3.0.x was kinda strange behaving...

[Andreas]

Reindexing depends on the server ;)

On my board (1.8 million posts, 4 GB RAM, Dual Xeon 2.8 with RAID 10 HDs mySQL only) it took some seconds for the thread table, and approx. 15 minutes for the post table.

Though, you're right about FT in 3.0

[Paul M]

It wouldn't take very long, this forum only has a few % more than ours and that managed inside 1/2 hour.

[dbembibre]

increase your php memory_limit to 16 or more mb