New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
paru -Syu will lock up with a mem-leak (?) when looking for devel updates #360
Comments
How many git packages do you have? Only thing I can think is you have so many it OMMs as they are all checked in parallel. |
I currently have 9 (nine) -git packages installed. I also have 16 gigs of RAM and another 16 gigs of swap, so that would be some rather badly optimized routine that would fill that outside of a bug... |
Yeah 9 wont be anything close to cause that. Are you experienced with debugging? Could you get a backtrack? |
Sure, if you could give me some pointers on what to do, I'll be happy to try to be helpful in debugging (can't guarantee I will, though, cause really not a software developer here...). |
While paru is running you can attach to it with GDB and print a backtrack with 'bt'. You'll need to run paru using cargo to get debugging symbols. |
Alternatively if you can limit how much ram paru is aloud to use it should panic from failure to allocate. |
OK, because I do not know how to do the things you asked me to do, I instead did something I DO know how to do (don't you just love testers like me?...) - I ran a git bisect.
Anything prior to this one runs fine, anything after this will run 100% on one cpu core until all available memory is filled and then crash the session. |
Interesting. Does it still lock up with |
Oh and with |
|
That's funny cause that commit only changed code in upgrade menu. What's your pacman version? |
|
And how about |
|
|
My guess would be It's a bug in the AlpmLIstMut code in the alpm bindings. That's going to be a bit of a pain to find. |
Does it work on the debug branch? I changed the code to not call .retain in cause that is the buggy function. |
Sorry, no dice, still crashes... :( |
I don't think I can do much more unless you manage to get a backtrace of where it's stuck or get an mre. |
OK, could you ELI5 for me how to get a backtrace, then? |
run paru, then in another terminal type |
This looks like it should be more helpful than it is.... What did I miss? |
|
Run paru through cargo. The package in the AUR is stripped of debugging symbols. |
Ah, this is where that whole ELI5 comes in again. Because I have no idea how that works. :) |
Would it work if I just compile it with |
Run |
That would work. Though if you don't know how to use cargo did you actually test the debug branch? |
|
Actually, it didn't...
|
The PKGBUILD compiles with |
|
|
|
This is from the debug branch. |
Now that's useful. Will look when I'm home. |
Line 97 in daf6f74
because @Taijian if you still have some time, would you mind editing that line in pad = db_pkg_max + 1 - (db.len() + pkg.len()) and see if that fixes anything? |
Nope, did not help...
|
Try the new master. It was just using the wrong dbs. |
That did it! New master is a good master! Taijian is a happy elf! |
Affected Version
paru v1.6.1 - libalpm v12.0.2
Description
When invoking
paru -Syu
, execution of paru will stall at theLooking for devel upgrades
stage. One CPU core will be utilized at 100% while RAM usage will start to climb indefinitely (until OOM hits).I am using a local repo for my AUR packages, which is configured in paru.conf and has been working fine until the latest update.
Output
~/.config/paru/paru.conf
See the paru.conf(5) manpage for options
GENERAL OPTIONS
[options]
PgpFetch
Devel
Provides
DevelSuffixes = -git # -cvs -svn -bzr -darcs -always
#BottomUp
RemoveMake
SudoLoop
#UseAsk
#CombinedUpgrade
CleanAfter
SortBy = popularity
NewsOnUpgrade
UpgradeMenu
BatchInstall
Rebuild = all
BuildDir = /home/gunnar/.cache/AUR
MovePkgs
LocalRepo = local_aur
Chroot = /home/gunnar/.chroot
Binary OPTIONS
#[bin]
#FileManager = vifm
The text was updated successfully, but these errors were encountered: