** Changed in: glib2.0 (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due
** Changed in: glib
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due to
heap corruption
** Changed in: mir/0.9
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due to
heap
** Changed in: mir
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due to
** Branch linked: lp:ubuntu/vivid-proposed/mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due to
heap corruption
This bug was fixed in the package mir - 0.10.0+15.04.20150107.2-0ubuntu1
---
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.10.0 (https://launchpad.net/mir/+milestone/0.10.0)
- Enhancements:
. Added support for
desrt just reminded me (after I reminded him :) that my apparent
explanation of the bug doesn't make sense.
We're losing a reference to the GSource and the claimed unsafe callback
should actually be safe already (as its caller is designed to hold a
ref).
Although the workaround that's landed
Fix committed into lp:mir at revision 2197, scheduled for release in
mir, milestone 0.10.0
** Changed in: mir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glib2.0 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided = Critical
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
Further to the test case in comment #8, you can reproduce the bug under
valgrind too (hence comment #9). Beware however that only triggers the
issue if you run _sufficiently_little_ clients so that performance is
still reasonable. So for me instead of 30+ egltriangles on valgrind I
use only 7 of
Upstream bugs seem to already exist for the issue:
https://bugzilla.gnome.org/show_bug.cgi?id=720186
and maybe:
https://bugzilla.gnome.org/show_bug.cgi?id=737677
** Bug watch added: GNOME Bug Tracker #720186
https://bugzilla.gnome.org/show_bug.cgi?id=720186
** Also affects: glib via
** Changed in: glib
Status: Unknown = New
** Changed in: glib
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since
** Changed in: mir/0.9
Status: In Progress = Triaged
** Changed in: mir/0.9
Assignee: Daniel van Vugt (vanvugt) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
The first, and probably the primary, error is this:
==18516== Invalid read of size 4
==18516==at 0x71F518A: g_source_iter_next (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4302.0)
==18516==by 0x71F7A7E: g_main_context_check (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4302.0)
==18516==
** Branch linked: lp:~vanvugt/mir/fix-1401488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
[regression] Mir servers (since 0.9) randomly crash in malloc due to
heap corruption
To
The regression came from this, so the bug just slipped into the 0.9.0
release too:
revno: 2072 [merge]
tags: br0.9, v0.9.0
author: Alexandros Frantzis alexandros.frant...@canonical.com
committer: Tarmac
branch nick: development-branch
18 matches
Mail list logo
