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 have no open tickets regarding memory leaks
which I interpret as evidence that there is no such problem for all other
distributions.

Today I tried to reproduce the issue without success:
after ~50 trivial SELECT queries mysql-workbench-bin uses

    VIRT  : 683M
    RES   : 75200
    SHR   : 41300

with ~10 threads.

It is a heavy application indeed but I see no problem you describe.

Would you be able to provide more information how to reproduce please?

Thanks.

Regards,
Dmitry.

When I start the workbench, it has 90m resident allocated. I run a "select now();" query two times, and resident grows to 102m. On the third run of the same query, resident jumps to 170m. On the fourth run, it runs to 1g in about 10 seconds, and starts into swap death.

I periodically update packages as they come available, and I recently updated from 5.2.38-something to 5.2.40 hoping to resolve occasional segfaults and missing schema trees. I thought maybe it was a problem with the previous ~/.mysql/workbench settings, so I renamed the .mysql directory and let it recreate it. That didn't help. I've done a remove and reinstall, but no difference.

I've compiled it from source as well, and I have the same problem. I've done straces and attached with gdb to try and track down where it starts leaking. So far it looks like it happens well after DbSqlEditorView::on_exec_sql_done(), during a bunch of Glib calls, though I haven't narrowed it down much more.

I had a couple coworkers try it. One is using aptosid, and he has no problem, the other is running Debian sid as well, and has no problem. I'm running native rendering as OpenGL doesn't work with my nouveau drivers. The other two are on intel graphics and an ATI card with proprietary drivers. One is on KDE4, the other is on Gnome3. It might be it's a problem in the native rendering and not discovered if everyone else is using OpenGL rendering, but that's just another stab in the dark at this point.

Grazie,
Daniel Fussell


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to