This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 233513

Summary:	org.openide.actions.PasteAction$ActSubMenuModel.getPasteTypesOrActions: LowPerformance took 10099 ms.
Product:	platform	Reporter:	javydreamercsw <javydreamercsw>
Component:	Actions	Assignee:	Jan Peska <JPESKA>
Status:	NEW ---
Severity:	normal	CC:	ebakke, jtulach, rkeen
Priority:	P3	Keywords:	PERFORMANCE
Version:	7.4
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	202575
Attachments:	nps snapshot When doing "Copy" on a folder in MacOS, this ends up on the clipboard

Description javydreamercsw 2013-07-26 19:22:13 UTC

This bug was originally marked as duplicate of bug 220821, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201307252300)
VM: Java HotSpot(TM) Client VM, 24.0-b53, Java(TM) SE Runtime Environment, 1.7.0_40-ea-b34
OS: Windows 7

User Comments:
javydreamercsw: Doing refactoring.



Maximum slowness yet reported was 10099 ms, average is 10099

Comment 1 javydreamercsw 2013-07-26 19:22:16 UTC

Created attachment 137878 [details]
nps snapshot

Comment 2 Jan Peska 2013-08-07 12:41:52 UTC

Jardo, do you have any idea why your fix from #220821 does not work in this case?

Comment 3 Ondrej Vrabec 2014-03-21 08:02:13 UTC

*** Bug 242917 has been marked as a duplicate of this bug. ***

Comment 4 Ondrej Vrabec 2014-03-21 08:04:38 UTC

Bug 242917 complains that every selection change triggers update of NbClipboard, that's wrong obviously, NbClipboard should be refreshed only once.

Comment 5 ebakke 2014-03-26 18:46:30 UTC

Created attachment 146338 [details]
When doing "Copy" on a folder in MacOS, this ends up on the clipboard

Another reason why this bug can show up during normal IDE use... whenever you "Copy" a folder in Finder on MacOS, a giant image of a folder ends up on the clipboard, which NetBeans promptly loads on the next Node selection. This caused an OutOfMemoryError in my platform application.