Last modified: 2013-05-02 17:51:33 UTC
Created attachment 11834 [details] Timeline of the cat crash Usually it just takes forever, especially waiting for bits (on Firefox); but I've tried now with Chromium and it crashed completely ("whoops"): 23.0.1271.95 Built from source for Fedora release 17 (Beefy Miracle) (169798). I don't know how to attach useful data, I made a screenshot of the timeline. U used "Cat" ([[wikidata:Q146]]) as example, the problem usually happens with bigger entries – I think –.
Created attachment 11835 [details] Firebug net and profiling top Note, comment 0 was as logged out and it's the same over HTTP. When logged in, on Firefox, it would seem that there's something weird about the logo and stewards banner? Don't ask me to export profiling data, last time I tried it was a huge waste of time.
Wild guess, soomething goes wrong in decoding the data urls. How dos it crashes? A sigsegv?
(In reply to comment #2) > Wild guess, soomething goes wrong in decoding the data urls. How dos it > crashes? A sigsegv? I don't know, I just saw the "whoops" page Chromium uses; Chromium is more picky than Firefox, so it might just have got sick of waiting.
Nemo: Is this reproducible? jeblad / Wikidata team: How to attach useful data?
(In reply to comment #4) > Nemo: Is this reproducible? I don't know what's "this", so I don't know how to reproduce. The symptoms, however, always happen to me when I open any Wikidata entry (maybe I'm opening only the wrong ones, no idea).
Try to clear out the browser cache, perhaps the problem goes away. Check if the problem repeat itself if you try to access the entries that has previously failed. Try to turn off all gadgets and see if the problem goes away. I can't reproduce this at my machine, but I (and the rest in the team) don't use the community gadgets.
It doesn't seem like there is anything wrong with the cat-entry. https://www.wikidata.org/w/api.php?action=wbgetentities&ids=q146
(In reply to comment #6) > I can't reproduce this at my machine, but I (and the rest in the team) don't > use the community gadgets. I was logged out in Chromium, so gadgets can't be the problem.
I've not seen this lately, although I tried opening some huge entries now and then; tentatively closing.
