There are broken images on election page of any SE site, e.g. on SO:


As suggested by PeterJ in comment opening the flair image leads to HTTP 500 error. Screenshot from the Chrome browser:

Chrome 500

  • 1
    Works here, Windows 10, Firefox 65.0 – Jenayah Feb 13 at 12:28
  • 2
    @Jenayah hmm ... looks fine with VPN too. Seems the Russian roskomnadzor issue – αλεχολυτ Feb 13 at 12:30
  • @αλεχολυτ, seem roskomnadzor not like αλεχολυτ :-D all works – Grundy Feb 13 at 12:32
  • 1
    Looks like an HTTP error 500 retrieving the flair icons: stackoverflow.com/users/flair/34397.png – PeterJ Feb 13 at 12:36
  • @PeterJ That link loads absolutely fine for me. Could be a geography-specific issue. – Sonic the Anonymous WizHog Feb 13 at 12:47
  • A similar issue with flair was pointed out in The Tavern yesterday. Personally, I can't reproduce either, but unless rene can see flairs now, it excludes geography-specific as rene and I are from the same small country. – Tinkeringbell Feb 13 at 12:49
  • No repro here, maybe related to Teams? Try to copy and paste URL of a broken image if it's still broken. – ShaWiz Feb 13 at 12:50
  • 1
    MSO report: meta.stackoverflow.com/q/380133/578411 – rene Feb 13 at 13:04
  • 1
    @Tinkeringbell using the different ISP also solve the issue. For instance, works on my phone via mobile network, and broken for my office ISP. – αλεχολυτ Feb 13 at 13:05

We had a web server that was misbehaving in ways that really don't make any sense, and as part of a debug of things, a reboot magically fixed it. System.Drawing (being swapped soon) was saving 0 byte files only on this box (ny-web05). This meant all users had a 1 in 9 chance of hitting the issue, for all flair from the box. Unfortunately System.Drawing throws an OutOfMemory exception for everything and is damn near useless in terms of debugging anything after-the-fact.

Since we're going to replace all this code for the .NET Core port here, I'm not advising we spend any more time digging into it...it's just not a good use of resources.

TL;DR: I know what it was doing, but not why it was doing it. And the symptoms are no longer there to debug. So we'll call this a fluke.

  • 3
    You happily ignored the warning in the remarks Classes within the System.Drawing namespace are not supported for use within a Windows or ASP.NET service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions. ;) thanks for the fix, you rock! – rene Feb 13 at 14:23
  • 1
    @rene yeah, but it worked for 9 years so... – Nick Craver Feb 13 at 14:24
  • Such a great and complex system and a simple reboot fixes all the problems... ;) – MEE was the missing bracket Feb 13 at 15:14

You must log in to answer this question.

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