Recurring bug with docker container: failed to get user: interrupted (9) about memos

[ozls]

In this case I have just one resource in the latest memos, a screenshot. I only ever attach photos or screenshots. It had been displayed before without issue, I don't know what changed. It definitely happened before 0.22.5.

[RoccoSmit]

What type of resources (attachments) are you viewing? Images?
And, do you get these errors when looking at new resources (ones you haven't looked at before) or does it happen with for e.g. reload the home page?
Did you have this issue in v0.22.4?

[RoccoSmit]

I was wondering if the new thumbnail feature was causing this, but if it happens before 0.22.5 then it's something else

[sherlcok314159]

0.22.2 also has this problem

[RoccoSmit]

I've not been able to reproduce this, if I had to take a stab in the dark it would be something to do with your browser telling the server to close the connection (context), the server being mid db activity and not unlocking the db and the subsequent db requests not being allowed due to the lock e.g. getting the user. but the code looks like its handling the connection closure so not sure and also not sure why your browser would tell the server to close the connection

Are you viewing large images?

[ozls]

I had this issue with both my laptop (Firefox) and my phone (Vanadium, a Chromium fork) so I don't think it comes from the browser. My images are all below 3MB.

But now that I think about it, it might have something to do with the way the container gets stopped. I run watchtower every night for updates, and before 0.22.5 I had memos on the stable tag, which means it got restarted frequently. Indeed memos has been running without issue for a few days, but I just managed to make it crash:

1. Browse my memos a little bit, load resources without issue
2. Stop and remove the container
3. Start up the container
4. Browse memos as fast as possible, as soon as the web UI was available

I managed to view a few images without issue, but one specific memos with three pictures made it crash. The images never appeared, no more memos could be loaded, the same log lines appeared and a blank screen was displayed on refresh.

Just after this I stopped, removed and started the container once more. I just waited a little bit, and then I was able to browse memos without any crash. I hope this helps!

[remsch]

I share the same problem (complete overlap, in my opinion), running the container version of Memos (v.0.22.5) on Coolify v.4.0.0-beta.325. I have two separate instances on two subdomains, both on SQLite, one runs fine, while the other doesn't. The problems occurred when I added another user I since deleted. Since deletion didn't resolve the problem, I suspect another issue.

[RoccoSmit]

@ozls do you always have the same successful web request before the first ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary or are they different