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.
| Summary: | New page in new project won't go into design view until I switch to other view first | ||
|---|---|---|---|
| Product: | obsolete | Reporter: | rdelaplante <rdelaplante> |
| Component: | visualweb | Assignee: | _ sandipchitale <sandipchitale> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | quynguyen, rdelaplante, wadechandler |
| Priority: | P3 | Keywords: | PERFORMANCE |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
visual web project
message log from around that time An other messages log |
||
|
Description
rdelaplante
2007-11-27 21:27:00 UTC
I forgot to mention this is RC2 on XP Pro, JDK 6u3 Hi, you say, it was gray but with the text inviting to add the components? Wasn't there the "Loading, please wait.." message? Also if you have, please, provide the log file. Thanks. For not I'll try to reproduce it. But I need more info. I was playing with it a bit but didn't reproduce it. Please provide more info, what was in the page, and the log file. Thanks. Yes like the grey "Loading, please wait..." screen, but without the text. I remember the first time it said please wait loading, then the text went away but the screen stayed grey. I will attach the web project and the last couple archived log files for you to peek at. Today I opened that screen and this time it rendered the white design area with a grid for me to start using. Created attachment 53612 [details]
visual web project
Created attachment 53613 [details]
message log from around that time
Created attachment 53614 [details]
An other messages log
The problem seems to be the OutOfMemoryError, which came when parsing the model. Passing to insync. Please, if that happens again, try to bump up your the memory for your jvm, that is all you could do for now. Also decreasing the priority. The OOME happened in Insync code...but we need to tack down the original memory leaks that consume the memory. I think it is worth noting the priority should not be so low. I point to: http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html Which states this to be a P1. Ryan has been using VWP for real work, and this is not only stopping him from using the feature, but it is also making him have to restart the entire IDE. He has some files he might be able to now share with a developer if that would help which might help track down the memory leak. He has some large files which he has recently mentioned on nbusers which he can reliably reproduce the memory leak by using the visual editor if that will help. He has created issue 123003 which might be the same thing, but he'll have to answer that. It might help to see what's going on by generating a heap dump then attach to the issue, using jmap included in Java 6 sorry, -please disregard, i forgot the size of the heap dump is too large to attach. If you have a server that to ftp into to retrieve the file At least with a single page project like the one you have attached I am not able to reproduce this issue. Had you opened the other 30 page project prior to opening this project? A lot of the issues related to memory consumption as well as performance has been fixed in 6.1. As such I am not able to reproduce it for small or large project. Please reopen with a specific case if it happens again. |