this post was submitted on 15 Nov 2025
99 points (96.3% liked)

Software Gore

6245 readers
3 users here now

Welcome to /c/SoftwareGore!


This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!

Remember to read the rules before you make a post or comment!


Community Rules - Click to expand


These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)


  1. This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
  2. Please keep all discussions in English. This makes communication and moderation much easier.
  3. Only post content that's appropriate to this community. Inappropriate posts will be removed.
  4. NSFW content of any kind is not allowed in this community.
  5. Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
  6. Do not repost media that has already been posted in the last 30 days. Such reposts will be deleted. Non-original content and reposts from external websites are allowed.
  7. Absolutely no discussion regarding politics are allowed. There are plenty of other places to voice your opinions, but fights regarding your political opinion is the last thing needed in this community.
  8. Keep all discussions civil and lighthearted.
    • Do not promote harmful activities.
    • Don't be a bigot.
    • Hate speech, harassment or discrimination based on one's race, ethnicity, gender, sexuality, religion, beliefs or any other identity is strictly disallowed. Everyone is welcome and encouraged to discuss in this community.
  9. The moderators retain the right to remove any post or comment and ban users/bots that do not necessarily violate these rules if deemed necessary.
  10. At last, use common sense. If you think you shouldn't say something to a person in real life, then don't say it here.
  11. Community specific rules:
    • Posts that contain any AI-related content as the main focus (for example: AI “hallucinations”, repeated words or phrases, different than expected responses, etc.) will be removed. (polled)


You should also check out these awesome communities!


founded 2 years ago
MODERATORS
top 19 comments
sorted by: hot top controversial new old
[–] Kolanaki@pawb.social 37 points 4 weeks ago* (last edited 4 weeks ago) (3 children)

8.6% of that is taken by your Faster Than Light drive.

[–] vrek@programming.dev 10 points 4 weeks ago (2 children)

8.6% of the processor or 8.6% of the total listed?

[–] bjoern_tantau@swg-empire.de 10 points 4 weeks ago (1 children)
[–] vrek@programming.dev 7 points 4 weeks ago (1 children)

They need to increase those numbers, Thanos got 50%

[–] homesweethomeMrL@lemmy.world 4 points 4 weeks ago (1 children)
[–] vrek@programming.dev 3 points 4 weeks ago (1 children)

Well go complain to Thanos

[–] hemmes@lemmy.world 2 points 4 weeks ago

Well go complain to the red floating guy

[–] Kolanaki@pawb.social 3 points 4 weeks ago (1 children)
[–] vrek@programming.dev 3 points 4 weeks ago

We need to buy more processors than....

[–] veroxii@aussie.zone 5 points 4 weeks ago

You can speed up your FTL jump calculations by networking together various other ship computers. But you risk the Cylons hacking your firewall before you're done.

It can get you out of a tight spot though. And later you can just restore your software from pre-invasion backups.

[–] PrimeMinisterKeyes@leminal.space 4 points 4 weeks ago* (last edited 4 weeks ago)

So the blue light emanating from my computer must be actually Cherenkov radiation.

[–] SkyezOpen@lemmy.world 7 points 4 weeks ago

I don't think you should overclock that much.

[–] x00z@lemmy.world 3 points 4 weeks ago

Are you using dry ice for this?

[–] ohshit604@sh.itjust.works 3 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

CPU usage measuring is weird on Linux, when top says CPU usage is at 200% and you start panicking.

[–] 4am@lemmy.zip 5 points 4 weeks ago

100% (I.e. Load Avg =1.0) is 1 core at full load

If you have 12 hyper threaded cores across 2 sockets then you’re not maxed until 48.0, or 4800%

It would be nice to see in terms of total system percentage but I get why it is the way it is

[–] SnekZone@lemmy.blahaj.zone 3 points 4 weeks ago (2 children)

Hey, I am not that deep into Tech, but isn't swap supposed to be unused if the RAM is like 15% full?

[–] 4am@lemmy.zip 7 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Not necessarily no. That’s how it used to work a long time ago but swap is also used to store infrequently accessed memory in order to help free up contiguous blocks. Even if your memory isn’t 100% full, if a program needs a large sequential block and can’t get it, this can also cause an out of memory error (one large block in physical memory is faster than trying to break it apart using virtual addressing to spread it across gaps - although I think modern OSes can do both but prefer the faster solution). Also, modern OSes LOVE to cache tons of stuff in RAM whenever they can and keep it there (unused RAM is wasted RAM), but they can’t act like memory is full if they are doing that! It would drive users nuts. So that cache can just be thrown away and then reloaded later when something more important needs RAM. However, what happens if you have say a file cached and it hasn’t been written to the proper disk location yet and you need to free up space? You can swap out the cache until you are ready to write it to its proper disk location.

Swap isn’t just “overflow RAM” anymore like how Virtual Memory was in O.G. Mac System 7, it’s got a lot of complex uses now in order to make sure that the user can get the most out of the computer, instead of getting errors and having to close things when all it would take to keep things smooth is a little re-arranging.

This is also why it’s a bad idea to “just turn off swap” for container hosts and K8 nodes - it’s not always the performance gain you think it will be (depends highly on your workload of course!) and you should instead be tuning it rather than disabling it!

[–] SnekZone@lemmy.blahaj.zone 3 points 4 weeks ago

Ah thanks, TIL!

[–] placatedmayhem@lemmy.world 4 points 4 weeks ago

About a decade ago, Linux switched to proactively swapping out inactive memory pages.