Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Why does this Data Explorer query explode (on Firefox 7.0.1, Mac OS X 10.6.8)?

Exploding query

I can run the query once, when I compose it for the first time, but all further attempts to access it from my profile or a permalink result in the JSON (?) dump above.

Working query

Any ideas?

share|improve this question
Just curious, what's the point of this query? – Pops Oct 26 '11 at 17:04
@PopularDemand I wrote this query as a response to a question that was asking for a way to search on close votes. Now that I have the query, I can't seem to find the question it was originally intended for... – Chris Frederick Oct 26 '11 at 17:27
I thought that might be it, but I didn't want to assume. Your results will be out of date (at least most of the time) because SEDE runs queries against a monthly data dump. Was this question the one you were thinking of? – Pops Oct 26 '11 at 17:32
@PopularDemand No, it had more recent activity than that. I think it was actually a complaint about being unable to find "failed" (i.e. expired) close votes. I agree that the results will be out of date, but they should still be sufficient to find votes that have been languishing in the system for a while. – Chris Frederick Oct 26 '11 at 17:36
@PopularDemand Ah, here's the question I was looking at. It had a +500 rep bounty from Pekka. – Chris Frederick Oct 26 '11 at 17:44
marking this as complete, let me know if it is still a problem – waffles Jan 10 '12 at 6:39
up vote 4 down vote accepted

One of the titles in the cached results is

Removing <script></script> block from returned html in C#

which causes the browser to prematurely terminate the surrounding </script> block. The JSON is supposed to have the / escaped specifically to avoid this, but I think some refactoring may have interferred with that for cached results that are loaded into the page directly.

I'll see what I can do about a quick-fix.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .