On Sat, 10 Nov 2012 09:26:40 Daniel Fussell wrote:
I checked the change log for the updated 1.8.15-3 version of the package
and saw the fix memory leak entry earlier. So I updated it, switched
back to qtcurves, ulimit-ed the virtual memory to 1.2GB, and started
mysql-workbench from that
Hi Dmitry,
Sorry for the slow response..
On Thursday 18 October 2012 01:59:23 Dmitry Smirnov wrote:
Could you please also try with
--force-sw-render
and
--force-opengl-render
to see if it have any effect on leak?
No difference at all.
Looks like problematic package is
Hi Dmitry,
I didn't get to test with the stock kernel, but I played a little with
valgrind and at one point (on 5-6 query) this starts to flood infinitely:
==12581== 9,749,448 bytes in 135,409 blocks are possibly lost in loss record
33,777 of 33,779
==12581==at 0x4C272B8: calloc
Hi Dragomir,
On Wed, 17 Oct 2012 23:38:28 Dragomir Dragnev wrote:
So i tested to change default GTK2 theme from QtCurve to Qt4 from system
settings and without kde restart tested mysql-workbench again with full
success no more memory leaks or anything - just looking ugly..
So for temporary
Package: mysql-workbench
Version: 5.2.44+dfsg-1~exp1
Followup-For: Bug #682162
Hi Dmitry,
I have the same effects like Daniel and 5.2.44 didn't make any difference
Executed from terminal:
$ mysql-workbench
Initializing AdvancedSidebar factory method
Initializing mforms factory
** Message: Gnome
Hi Dragomir,
Thank you for detailed report.
I'm on KDE as well and I have the very same set of libraries installed yet I
can't reproduce the issue. The only difference between our configuration that
I've spotted is kernel -- I have Linux 3.2.0-3-amd64 installed.
Could you try with Linux
Hi Daniel,
I'm sorry to read about your troubles.
Upstream just released 5.2.41 I hope it might work better for you.
I did preliminary packaging - you may want to check branch 5.2.41 from
http://anonscm.debian.org/gitweb/?p=collab-maint/mysql-workbench.git
You can get DFSG-repackaged
On 07/20/2012 07:01 PM, Dmitry Smirnov wrote:
Hi Daniel,
Thanks for your report.
It is a bit puzzling since just a week ago I was using M-W for several hours a
day and I didn't even bother to restart it for a week - I was just suspending
my workstation instead.
Also I've noticed that upstream
Hi Daniel,
Thanks for your report.
It is a bit puzzling since just a week ago I was using M-W for several hours a
day and I didn't even bother to restart it for a week - I was just suspending
my workstation instead.
Also I've noticed that upstream have no open tickets regarding memory leaks
Package: mysql-workbench
Version: 5.2.40+dfsg-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Entering and running 3 queries in the workbench SQL editor,
with a maximum of
3
10 matches
Mail list logo
