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 181795 - High memory usage when executing a query
Summary: High memory usage when executing a query
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal with 2 votes (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-10 11:57 UTC by Simz
Modified: 2012-09-29 21:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profile (71.11 KB, application/octet-stream)
2010-03-10 11:57 UTC, Simz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simz 2010-03-10 11:57:17 UTC 
Overview:

  High memory usage when executing a db query (~350mb to 500mb).
  The MySQL database has 182 tables.
  the query is select 1=1;



Steps to Reproduce:

  Start Netbeans
  Choose "execute command" inside the a saved database connexion (Database service)

Actual Results: 

    Memory usage jump from 30mb to ~350mb

Tested
    I can't reproduce this bug in 6.7.1
    
Infos:

Product Version: NetBeans IDE 6.8 (Build 200912041610)
Java: 1.5.0_19; Java HotSpot(TM) Client VM 1.5.0_19-b02
System: Linux version 2.6.31.12-174.2.22.fc12.i686.PAE running on i386; UTF-8; en_US (nb)
Comment 1 Simz 2010-03-10 11:57:50 UTC 
Created attachment 95009 [details]
profile
Comment 2 Simz 2011-03-14 20:18:43 UTC 
still not fixed. Are you planning to fix that ?
do you need more info ?
Comment 3 Jiri Rechtacek 2011-03-15 08:12:30 UTC 
Not planned to fix it in NB7.0.
Comment 4 matthias42 2012-09-29 21:47:26 UTC 
This is not reproduzible in 7.2 - I got this with visual vm:

- After start: ~250MB Heap usage
- After forced GC: ~100MB Heap usage
- While connecting (without GC collection!): 175MB
- forced GC: ~100MB
- Editor opened (without GC collection!): 200MB
- forced GC: ~100MB
- Query opened (without GC collection!): 194MB
- forced GC: ~100MB

This is big, but remember: Your looking at a very massive system.

Closing as no connection to the DB module is verifyable and the memory situation looks pretty normal.