By doing this, you are adding multiple times the same rules to the bbcode parser, indeed it can create some confusion, and i won't be surprised if it created memory leaks, i'll do a double check around existing tags being re-added, 

But the bbcode_add_element($parser,$tag, $option);

Should only be called "once" per tag, so, outside of the loop.

Can you confirm the bug exists with the following code?

(Don't have a test-env at hand)

$parser = bbcode_create($options);
$text = "this is an [url=http://google.com]example link[/url].\n";

foreach ($options as $tag => $option) bbcode_add_element($parser,$tag, $option);

for ($i=0; $i<1000; $i++)
{
    echo(bbcode_parse($parser, $text));
}

Thank you for your very fast reply. Removing that does 
indeed take away the problem. But that is not a workable 
solution for us, as the script was just a demonstration that 
there is a memory problem in the bbcode extension, and not a 
demonstration of a very efficient and smart use of the 
bbcode extension :).

We are using this extension on a website with many texts 
that all have bbcode in them. What we do is this: we first 
create the parser with all the elements, add smilies, and 
then we call bbcode_parse(...) a number of times for all 
texts on the page.

However: it turns out that by doing this, we caused the 
apache process to crash with a segmentation fault once in a 
while. It just crashed, and the php error log was filled 
with strange errors like "function `xxx' is not a function 
name", where xxx was some substring out of the text being 
parsed. Sadly, I have not managed to create a reproducable 
situation that triggers this error.

We could work around this problem by re-adding the elements 
that use callback functions right before each call to 
bbcode_parse. That is indeed odd and should not be 
necessary, but it did solve the segmentation fault problem. 
But today I found out that now suddenly some articles are 
not being parsed and still show the original bbcode instead 
of the html code. The script that I posted with my original 
bug report is just a small demonstration of this problem.

What is also strange: if you change the example script 
slightly, and add a 'b' tag instead of a 'sub' tag, the 
problem is gone too! It really looks like a buffer overflow 
or accidental memory deallocation.

I really hope the problem can be solved. Our current 
workaround is to setup a new parser for every single text 
that needs to be parsed. But this is not very efficient 
because we have so many smilies that we have to loop over.

Indeed, for your production settings, i'll strongly recommand recreating the base parser, as adding all element everytime will be even less efficient :)

I'll try to investigate this asap.

Thanks a lot for your feedback,

Xavier.

What version of the extension are you using?

Hi Xavier,

The problem occurs on both the current stable and the current 
beta release, 1.0.2 and 1.0.3b1.

Emiel

Due to this extension not seeing any activity since 2010, this issue will not be fixed. We are therefore closing this now.