New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Circular reference in category causes "Segmentation fault" due to "Maximum function nesting level of '256' reached..." #1713
Comments
Whoo ... "Segmentation fault", no idea. |
The report is a bit sparse, any information from the PHP log or Apache log since "Segmentation fault" only happens on the PHP stack. |
That makes two of us. Let's see if others come up with it, too. My feeling is that the wiki is somehow borked because of the previous time of "neglectance". |
Luckily you were able to run with "--ignore-exceptions --exception-log" |
This did not help I am afraid. The script stopped every time and a log was not created either. |
What happens when you run one of the mentioned pages individually? |
That's right because its not an exception but a fault which happens on the "deep" PHP side without MW or SMW application involved. |
No change, just "Segmentation Fault". :( |
Anything in the php_error.log or Apache error.log? |
error.log:
So not really helpful. |
We are getting to it with
The lines I omitted are identical. |
Nice, it will take me a while to figure what's going here. |
Could paste the whole report into a gist and linked it here. |
https://gist.github.com/kghbln/c54a276e1110b79f0fb1a433e77804d4 |
Somehow a category (or a redirect thereof) is pointing to itself which cause the |
@kghbln Could you try applying the following patch.
|
A simple use case the provide some context.
|
Similar happens when you do:
|
Guard against circular reference in category/property hierarchy, refs #1713
The script is running now without segmentation faults. However it appears to be substaniallly slower and starting with ID 84 I am getting a loop:
now at 500+ loops for ID 84. Hmm .... Edit: I just stopped at loop 600+ and restarted the script with -s 85. So far no further loop. |
Need to investigate! |
I now see a pattern with the next loop I ran into:
So it is probably something on the Demo:Berlin page |
Same for Demo:London:
When trying to edit the page I get:
|
Different cause, and I have an Idea why ... so just hold the horses. |
Will do. Keeping fingers crossed. |
Can you update |
Just for the curious, I changed onoi/blob-store@053b1ed and this comes into effect with 1.2.1. |
@kghbln When you look at the |
I tried to verify that observation by comparing master against changes before #1714 on a local sample but I could not establish this fact. Sampling:
|
Currently I'm unsure where those loops coming from (maybe some rogue redirects):
See my comments in #1713 (comment). |
Indeed since the segmentation faults triggered are no longer detectable. |
I suspect this is due to the fact that xdebug is still kicking in somehow. |
Yes (I remembered to tell you to disabled it after it is no longer required but without it we wouldn't have found the cause.) |
Setup and configuration
Issue
When running "rebuildData.php" with
on smw.o heaps of segmentation faults are issued without further information.
The text was updated successfully, but these errors were encountered: