[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 User mba changed the following: What|Old value |New value Target milestone|OOo 2.x |OOo 3.x --- Additional comments from [EMAIL PROTECTED] Fri Jan 11 09:37:17 + 2008 --- target 3.x - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 User mba changed the following: What|Old value |New value Issue type|PATCH |DEFECT --- Additional comments from [EMAIL PROTECTED] Fri Oct 20 01:12:21 -0700 2006 --- As there is no patch attached I change the type to defect - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 User cd changed the following: What|Old value |New value Status|NEW |STARTED --- Additional comments from [EMAIL PROTECTED] Mon Sep 11 23:24:31 -0700 2006 --- cd: Accepted. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68973
User fs changed the following:
What|Old value |New value
CC|''|'fs'
Assigned to|fs|cd
Status|STARTED |NEW
--- Additional comments from [EMAIL PROTECTED] Wed Sep 6 00:14:04 -0700
2006 ---
okay, simply opening the file menu already exposes the leak: The
MenuFloatingWindow which is created then is destroyed upon closing the menu, but
the respective VCLXWindow is never disposed, only destroyed.
Normally, I'd say that ~VCLXWindow needs a
if ( !mbDispose )
{
acquire();
dispose();
}
, which is the usual pattern for this case. However, I'm uncertain about the
side effects - there might code behaving strangely if we do this.
So,
{
::vos::OGuard aGuard( GetMutex() );
if ( mpImpl )
{
mpImpl-disposing();
mpImpl-release();
mpImpl = NULL;
}
}
might be safer, though still leaking other instances (e.g. the A11Y potentially
component associated with the window.)
fs-cd: Your first AWT-issue? :)
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 User pl changed the following: What|Old value |New value Assigned to|pl|fs --- Additional comments from [EMAIL PROTECTED] Mon Sep 4 02:19:14 -0700 2006 --- pl-fs: please have a look - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 User fs changed the following: What|Old value |New value Status|NEW |STARTED Target milestone|--- |OOo 2.x --- Additional comments from [EMAIL PROTECTED] Mon Sep 4 02:29:02 -0700 2006 --- Hmmm would be interested in a scenario for this. Do you have a chance testing whether the VCLXWindow in question is being disposed? The release call to mpImpl should happen in VCLXWindow::dispose, and I would have expected that every VCLXWindow is disposed finally (though, ~VCLXWindow is missing the safety-cleanup call to dispose). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 --- Additional comments from [EMAIL PROTECTED] Mon Sep 4 04:45:52 -0700 2006 --- fs: will try to collect some data for you tonight. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[gsl-issues] [Issue 68973] leaks: toolkit and destroy ing VCLXWindow
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=68973 Issue #|68973 Summary|leaks: toolkit and destroying VCLXWindow Component|gsl Version|680m182 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|pl Reported by|pjanik --- Additional comments from [EMAIL PROTECTED] Sat Aug 26 06:19:48 -0700 2006 --- Hi, while debugging Mac OS X native port's svdem with added FullScreen function for testing, I realized that VCLXWindow class leaks 48 bytes: Leak: 0x0313ffb0 size=48 0x06318348 0x0001 0x027eb308 0x007e84ec .1.H.~...~.. 0x 0x 0x 0x 0x 0x 0x0313fea0 0x0003 Call stack: [thread 2717]: | 0x0 | start | _start | sal_main | Main() | Application::Execute() | Application::Yield(bool) | AquaSalInstance::Yield(bool, bool) | SendEventToEventTarget | SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) | DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) | ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) | HandleMouseEvent(OpaqueEventRef*) | HandleMouseEventForWindow(OpaqueWindowPtr*, OpaqueEventRef*, unsigned short) | SendEventToEventTarget | SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) | DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) | HandleMouseUpDownEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) | ImplWindowFrameProc(void*, SalFrame*, unsigned short, void const*) | ImplHandleMouseEvent(Window*, unsigned short, unsigned char, long, long, unsigned long, unsigned short, unsigned short) | MenuBarWindow::ChangeHighlightItem(unsigned short, unsigned char, unsigned char, unsigned char) | MenuBarWindow::ImplCreatePopup(unsigned char) | PopupMenu::ImplExecute(Window*, Rectangle const, unsigned long, Menu*, unsigned char) | MenuFloatingWindow::MenuFloatingWindow[in-charge](Menu*, Window*, long long) | FloatingWindow::FloatingWindow[not-in-charge](Window*, long long) | FloatingWindow::ImplInit(Window*, long long) | ImplBorderWindow::ImplBorderWindow[in-charge](Window*, long long, unsigned short) | ImplBorderWindow::ImplInit(Window*, long long, unsigned short, SystemParentData*) | Window::ImplInit(Window*, long long, SystemParentData*) | Window::IsTopWindow() const | Window::GetComponentInterface(unsigned char) | UnoWrapper::GetWindowInterface(Window*, unsigned char) | CreateXWindow(Window*) | VCLXWindow::VCLXWindow[in-charge]() | operator new(unsigned long) I think that the destructor of VCLXWindow is missing call to mpImpl-release(). Consider this as PATCH issue then ;-) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
