this post was submitted on 04 Jul 2023
2159 points (99.0% liked)

Lemmy.World Announcements

28382 readers
5 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages πŸ”₯

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations πŸ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 1 year ago
MODERATORS
ruud@lemmy.world
lwadmin@lemmy.world
lwCET@lemmy.world
jelloeater85@lemmy.world
Serinus@lemmy.world
lw_mod_notification@lemmy.world
2159
Lemmy.world status update 2023-07-04 (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world
318 comments fedilink hide all child comments
 

Status update July 4th

Just wanted to let you know where we are with Lemmy.world.

Issues

As you might have noticed, things still won't work as desired.. we see several issues:

Performance

  • Loading is mostly OK, but sometimes things take forever
  • We (and you) see many 502 errors, resulting in empty pages etc.
  • System load: The server is roughly at 60% cpu usage and around 25GB RAM usage. (That is, if we restart Lemmy every 30 minutes. Else memory will go to 100%)

Bugs

  • Replying to a DM doesn't seem to work. When hitting reply, you get a box with the original message which you can edit and save (which does nothing)
  • 2FA seems to be a problem for many people. It doesn't always work as expected.

Troubleshooting

We have many people helping us, with (site) moderation, sysadmin, troubleshooting, advise etc. There currently are 25 people in our Discord, including admins of other servers. In the Sysadmin channel we are with 8 people. We do troubleshooting sessions with these, and sometimes others. One of the Lemmy devs, @nutomic@lemmy.ml is also helping with current issues.

So, all is not yet running smoothly as we hoped, but with all this help we'll surely get there! Also thank you all for the donations, this helps giving the possibility to use the hardware and tools needed to keep Lemmy.world running!

you are viewing a single comment's thread
view the rest of the comments
[–] donalonzo@lemmy.world 19 points 1 year ago* (last edited 1 year ago) (1 children) 
let mut memory_leak = Vec::<u8>::new();
loop {
  memory_leak.push(0);
}
[–] meisme@lemmy.world 10 points 1 year ago (1 children)

That's not a memory leak though. That's just hording memory. Leaked memory is inaccessible.

[–] preciouspupp@sopuli.xyz 6 points 1 year ago (1 children)

In the example it’s inaccessible.

[–] meisme@lemmy.world 4 points 1 year ago (1 children)

It's not. The vec is still accessible and if it goes out of scope rust automatically clears the memory.

[–] crate_of_mice@lemmy.world 2 points 1 year ago (2 children)

But it will never fall out of scope because of the loop

[–] meisme@lemmy.world 4 points 1 year ago (1 children)

Exactly but it's still accessible since it's in scope.

[–] crate_of_mice@lemmy.world 1 points 1 year ago (1 children)

Right but where does it say that something has to be inaccessible to qualify as a memory leak?

[–] meisme@lemmy.world 1 points 1 year ago (1 children)

"A memory leak is a process in which a program or application persistently retains a computer’s primary memory. It occurs when the resident memory program does not return or release allocated memory space, even after execution, resulting in slower or unresponsive system behavior." Source

[–] preciouspupp@sopuli.xyz 1 points 1 year ago* (last edited 1 year ago)

That’s not a serious source. Any unbound allocation is a memory leak if it serves no useful purpose.