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.
This is related to http://www.netbeans.org/issues/show_bug.cgi?id=86942. While working on 86942, I discovered that another issue I filed earlier has resurfaced. That earlier issue was http://www.netbeans.org/issues/show_bug.cgi?id=75588. Normally I'm not able to reproduce 75588, however when you refactor TPA_Extensions in OTA schema using the enterprise pack, I can clearly reproduce and the hotspots are again: 1. DocumentModel.updateModel() 2. DocumentModel.DocumentModelModificationTransaction.removeDE() I can also see a lot of debug messages in the console coming from classes in package org.netbeans.modules.editor.structure.api.
It is not clear to me what the problem is and where it is. What are the steps to reproduce and what happens? What are the messages coming from org.netbeans.modules.editor.structure.api? Marking as INCOMPLETE, waiting for more input.
1) please attach the messages.log or the console output with the messages from the rg.netbeans.modules.editor.structure.api. 2) attach some threaddumps done while the 100% CPU load 3) can you please provide an exact list of steps to reproduce the problem? Thanks.
Evn though, the schema validation passes, while building the axi model, some schema components are null. In this case, the base for a complex extension is null. I'll have to take care of this situation. Ideally it shouldn't happen. In any case I'm going to integrate a fix, but the problem remains, that is DV shows up after the fix, but IDE is still unresponsive and CPU consumption is 100%.
Ignore my last comments. I updated the wrong issue. I'll update this one with more info.
Here is how you can reproduce the problem: - build enterprise pack. cd nbbuild/entpack ant soa - run the ide - open the attached schema (OTA) - Click on elements, you'll see some elements to the right - right-click on TPA_Extensions and refactor-rename to say TPA_Extensions1 - you'll see the preview window, click refactor - refactoring will finish in few seconds but the CPU gets busy even after refactoring is done. check the attached thread-dump and the console log that I have. I do not have the log file anymore.
Created attachment 35248 [details] OTA Schema
Created attachment 35249 [details] console messages
Created attachment 35250 [details] thread dump
Reassigning to default owner of selected subcomponent. New owners are gladly welcomed.
This was filed by me long time back and I know you did some work. The traces were originally coming from editor.structure.api and I do not see any updates from you after my inputs.
No, I didn't do any changes related to this issue AFAIK so the issue is still valid.
Hi Samaresh, could you please check this problem now? The fixes done to issue #89277 affects also CPU performance, not just memory consumption. Thanks.
I'm sorry, the situation is worse now. IDE remains unusable for atleast 3mins and I had to kill it. I can clearly see a lot of output in the console, just keeps coming....never stops. **** = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27981029)["..." (content) <713348-713348> ''] [DMT] removed element DE (27981029)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27980464)["..." (content) <713348-713348> ''] [DMT] removed element DE (27980464)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27974364)["..." (content) <713348-713348> ''] [DMT] removed element DE (27974364)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27969072)["..." (content) <713348-713348> ''] [DMT] removed element DE (27969072)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27962822)["..." (content) <713348-713348> ''] [DMT] removed element DE (27962822)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27962205)["..." (content) <713348-713348> ''] [DMT] removed element DE (27962205)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27960095)["..." (content) <713348-713348> ''] [DMT] removed element DE (27960095)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27959423)["..." (content) <713348-713348> ''] [DMT] removed element DE (27959423)["..." (content) <713348-713348> ''] ;parent = DE (28042396)["xs:schema" (tag) <250-819584> '<xs:schema...'] [DTM] removing DE (27957838)["..." (content) <713348-713348> ''] ****
OK, I'll try to reproduce. BTW, thanks for finding the forgotten debug message :-)
I have improved the DocumentModel update a bit, the peformance save is about 300% on the sample file. However the biggest bottleneck in the testcase is the XML folding. The used algorith - model fires change events - folding is synchronously updated is not effective and if there is a big change in the document then the performance is terrible. I'll fix this ASAP. Checking in DocumentModel.java; /cvs/xml/tageditorsupport/src/org/netbeans/modules/editor/structure/api/DocumentModel.java,v <-- DocumentModel.java new revision: 1.37; previous revision: 1.36 done
I ment that the the perf is 3 times better of course :-)
After Marek's changes this is a lot better. Marking this as fixed.