unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: problem merging from bzr
Date: Wed, 18 Apr 2012 20:12:05 +0300	[thread overview]
Message-ID: <83k41d6k2i.fsf@gnu.org> (raw)
In-Reply-To: <m3liltezu5.fsf@chopper.vpn.verona.se>

> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Wed, 18 Apr 2012 19:04:18 +0200
> 
> >> Notice the "Killed" message in there. This is when I try to merge my
> >> "xwidgets" branch from upstream.
> >
> > Could be OOM (out-of-memory) kill by the OS.  Look for relevant
> > messages in /var/log/messages (assuming this is GNU/Linux).
> 
> In dmesg:
> [140591.887966] Out of memory: Kill process 1898 (bzr) score 642 or sacrifice child
> 
> Interesting.
> 
> Some more statistics, since I seem to have forgot that in my last mail:
> 
> Fedora 17 Beta (So could be the culprit of course, but its stable otherwise)
> 
> Bazaar (bzr) 2.5.0
>   Python interpreter: /usr/bin/python 2.7.3
>   Python standard library: /usr/lib64/python2.7
>   Platform: Linux-3.3.1-5.fc17.x86_64-x86_64-with-fedora-17-Beefy_Miracle
>   bzrlib: /usr/lib64/python2.7/site-packages/bzrlib
>   Bazaar configuration: /home/joakim/.bazaar
>   Bazaar log file: /home/joakim/.bzr.log
> 
> (I upgraded to get this version and co-located branches)
> 
> The machine is a Core i7, 6GB ram

I guess you should report this to the Bazaar list, if not file a bug
report.  (I would start with the list, since they could offer some
workaround or maybe some secret switch to get more detailed debug info
that would explain why this happens.)



  reply	other threads:[~2012-04-18 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 10:25 problem merging from bzr joakim
2012-04-18 16:39 ` Eli Zaretskii
2012-04-18 17:04   ` joakim
2012-04-18 17:12     ` Eli Zaretskii [this message]
2012-04-18 17:42       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k41d6k2i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).