Bug 266114 - Add Export feature to sleak
Summary: Add Export feature to sleak
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 07:17 EST by Jacek Pospychala CLA
Modified: 2021-11-12 11:43 EST (History)
3 users (show)

See Also:


Attachments
export errors patch (3.10 KB, patch)
2009-03-11 07:47 EDT, Jacek Pospychala CLA
no flags Details | Diff
export errors patch v2 (3.95 KB, patch)
2009-03-25 10:24 EDT, Jacek Pospychala CLA
no flags Details | Diff
eclipse sleak plug-in for testing (12.66 KB, application/java-archive)
2009-03-25 10:37 EDT, Jacek Pospychala CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jacek Pospychala CLA 2009-02-25 07:17:29 EST
My end users happen to experience SWT leaks and while they're able to collect additional information using Sleak, it's hard for them to send that data to me - because of the amount of collected data.
So I propose adding "Export" option to Sleak view that would create a text file with all the contents from the view.

I'll try to implement that within next couple of days, unless there's already some other solution.
Comment 1 Felipe Heidrich CLA 2009-02-25 11:20:44 EST
Feel free the contribute (i don't know of any other solution for the problem)
Comment 2 Carolyn MacLeod CLA 2009-02-25 11:43:01 EST
That sounds like a useful feature to add, and your contribution is welcome.
I will test it and add it to the latest as soon as you attach it to this bug.

Just to make sure you know where the latest code is, you can find it in the eclipse cvs repository...

  :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse

  in the org.eclipse.swt.tools project.
Comment 3 Jacek Pospychala CLA 2009-03-11 07:47:31 EDT
Created attachment 128365 [details]
export errors patch

With this patch, sleak has new button "Print", that prints out all the stack traces to standard output. Was trying to keep this as simple as possible similarly to the rest of Sleak code.
Carolyn, please review when you have some time.

btw. I don't see where is Sleak plug-in view implemented, where is it?
Comment 4 Jacek Pospychala CLA 2009-03-20 10:25:22 EDT
Carolyn, when would you have time to look on that? (going to EclipseCon?)
Comment 5 Carolyn MacLeod CLA 2009-03-24 10:38:05 EDT
I'm not at EclipseCon, but I was away last week for Spring Break.
I'll try to get to this before the end of this week.
I have a lot of catch-up work to do first, because of my week away.
I believe that bug 269383 has the information you need about the location of the SLeak plug-in and owner.
Comment 6 Jacek Pospychala CLA 2009-03-24 10:59:14 EDT
Carolyn, good to hear from you.
I was looking for sources of platform-swt-home/tools/org.eclipse.swt.sleak.zip.
But now I see, they're simply inside that zip :-P
Comment 7 Jacek Pospychala CLA 2009-03-25 10:24:15 EDT
Created attachment 129842 [details]
export errors patch v2

Updated couple of things to make it easier for regular users to collect dumps.
Now user enables "Dump to file" checkbox. Later on, whenever he presses Snap or Diff, dump is written to file in current working dir.
Comment 8 Jacek Pospychala CLA 2009-03-25 10:37:42 EDT
Created attachment 129844 [details]
eclipse sleak plug-in for testing

binary plug-in org.eclipse.swt.sleak updated with patch v2 for others to test.
Comment 9 Eclipse Webmaster CLA 2019-09-06 15:36:08 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.