Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: Broken link to "Cool Uses For Perl" ("fixed")

by tye (Sage)
on May 03, 2013 at 04:40 UTC ( #1031822=note: print w/replies, xml ) Need Help??

in reply to Broken link to "Cool Uses For Perl"

This is an old problem that only triggers if all of the following happen at once:

  • The request is handled by a specific PM web server
  • A node on the page uses <spoiler> tags
  • Inside of the <spoiler> tags are <code> tags
  • The code is over 32kB or expands to over 32kB when expanded (maybe?) because...
  • The viewing user has a complex "Code Prefix" configured (or similar)
  • At least one other condition that I have not yet identified (perhaps related to how recently Apache has been restarted?)

And then what happens is that the Apache child dies due to "illegal instruction".

See also Re^5: "Invisible" nodes (details) (which includes an example thread that isn't currently failing for me even though I'm currently able to trigger the failure via other means).

Note that trying to combine all of those items together outside of Apache doesn't generate even a warning nor invalid results, even on the same version of Perl that Apache claims to have been linked against. Also note I've yet to figure out any way to get the failing case to tell me any hint about which of the many lines of code involved is where the failure happens (so I could just change it somewhat randomly so that it does the same things but just stops dumping core in that version of Apache).

In the mean time, I replaced a few uses of <spoiler> tags that weren't being used to hide spoilers with <readmore> tags so Cool Uses for Perl should load for everybody no matter which web server they hit (until the next person does that again).

Sorry for the inconvenience.

(Updated a few times in fairly minor ways after posting)

- tye        

Replies are listed 'Best First'.
Re^2: Broken link to "Cool Uses For Perl" ("fixed")
by Anonymous Monk on May 03, 2013 at 06:28 UTC

      That was a good one. It had almost a full 64kB of text inside of the spoiler tags and so failed extra often (even sometimes, but not always, on other web servers).

      So I found a possible culprit in an overly complex regex and I think the problem is completely gone now. Hard to say that with complete confidence when the problem can be so inconsistent in whether or not it happens, of course.

      - tye        

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1031822]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (4)
As of 2023-02-08 22:59 GMT
Find Nodes?
    Voting Booth?
    I prefer not to run the latest version of Perl because:

    Results (44 votes). Check out past polls.