** Tags added: patch-forwarded-upstream
** Tags added: patch
** Tags removed: patch-forwarded-upstream
** Summary changed:
- [patch] Upgrade tool crashed with Cannot allocate memory
+ Upgrade tool crashed with Cannot allocate memory
--
Upgrade tool crashed with Cannot allocate memory
is that still an issue in karmic or lucid? the bug didn't get new
duplicates or comment for months now
** Changed in: update-manager (Ubuntu)
Status: Confirmed = Incomplete
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received
Sebastien, I will be upgrading my laptop from Kubuntu 8.04 to 10.04 one
of these days, so I will post back here. Frankly, I am scared to
upgrade, but it will be a good test because it is double upgrade from
8.04 to 9.10 and then to 10.04 (Kubuntu doesn't support a direct
upgrade).
--
[patch]
@Nikolaus Rath: What specs did your system have? How much mem/swap? This
error is even earlier than most of the problems described in the report,
it fails already when calling uname -r.
I wonder if for the others:
=== modified file 'DistUpgrade/DistUpgradeController.py'
---
It's a Strato virtual server:
nikra...@ebox:~$ uname -a
Linux ebox 2.6.18-028stab064.7 #1 SMP Wed Aug 26 13:11:07 MSD 2009 i686
GNU/Linux
nikra...@ebox:~$ free
total used free sharedbuffers cached
Mem: 5122676 2240964898580 0
---
Linux dexter.vps 2.6.18-128.2.1.el5.028stab064.7 #1 SMP Wed Aug 26
15:47:17 MSD 2009 i686 GNU/Linux
---
total used free sharedbuffers
cached
Mem: 1024000 629444 394556 0 0
0
-/+ buffers/cache: 629444 394556
Swap:
This is happening on a sudo do-release-upgrade from intrepid to jaunty
in a virtual machine
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tools
Done downloading
extracting 'jaunty.tar.gz'
authenticate 'jaunty.tar.gz' against 'jaunty.tar.gz.gpg'
Reading
Hi,
It's only set to invalid for Baltix, it is still confirmed in
Ubuntu.
Thanks,
James
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: update-manager (Ubuntu)
Status: Confirmed = Invalid
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Why was this set to invalid. The defect still occurs and has been
confirmed. No fix for it has yet been released. It may not be against
the original packages that we thought, having been traced to a
dependency, but it is still an outstanding defect, and the status
invalid is not at all
why set to invalid?
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Try this:
valgrind /usr/bin/update-manager
*OUCH*
That's more memory-errors than I can copy-paste!!
Somebody needs to debug python2.5. This is a horrible mess!!
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received this bug
Sorry, this is a dead end road.
Using the correct suppression file and python-dbg, all errors disappeared (they
are false positives) ,
until it crashed because it can't find some gtk lib.
On a second attempt, using the correct suppression file and python without
debugging symbols, my system
For those interested, I tried this:
apt-get install python2.5-dbg valgrind
then, edit your /usr/bin/update-manager, line 1:
#!/usr/bin/python2.5-dbg
Then:
valgrind --log-file=python-errors /usr/bin/update-manager
This produced the attachment, and then said:
Traceback (most recent call last):
There are specialized memory debugging tools, for example valgrind.
If any attempt to allocate memory would fail, I would suspect that
valgrind would be able to give a nice stack trace. (recompile python
without optimization with debugging symbols!)
refer to
@BigPick: Thanks for your analysis of the patch, when I read it I was
wondering what change in it might have caused that the problem got
fixed. My current theory is that the bug occur more or less random (or
with a pattern that is very hard to reproduce) so that even if the patch
itself has little
OMG its Michael! Thank goodness your here!
Forgive my moronic meddling, I obviously have absolutely no clue what I
am doing. I went over my patch again and realized that my changes to the
commit retry loops:
-currentRetry = 0
fprogress = self._view.getFetchProgress()
Thanks for the comments on this bugreport and sorry for the trouble this
is causing.
@BigPick: Thanks a lot for taking the time to investigate the mater so
closely. If you can reproduce the problem reliably I would love to get
in touch with you directly so that we can debug it together. If you
** Summary changed:
- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory
+ [patch] Upgrade tool crashed with Cannot allocate memory
--
[patch] Upgrade tool crashed with Cannot allocate memory
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you
19 matches
Mail list logo
