I work at M*Modal, a large software company that makes natural language processing and understanding software for the health care industry, doing anything that needs doing (e.g. prototyping, bootstrapping, support), like an engineering SWAT team.
Areas of expertise:
- C#
- Windows Forms
- Windows Installer
- WiX
- WPF
- Continuous Integration
|
Apr
19 |
|
awarded | Famous Question |
|
Feb
26 |
|
awarded | Caucus |
|
Feb
5 |
|
awarded | Informed |
|
Jan
22 |
|
awarded | Revival |
|
Jan
19 |
|
awarded | Yearling |
|
Jan
18 |
|
awarded | Enlightened |
|
Jan
18 |
|
awarded | Nice Answer |
|
Jan
15 |
|
awarded | Fanatic |
|
Jan
13 |
|
awarded | Popular Question |
|
Jan
8 |
|
answered | How to set config output to special folder (LocalApplicationData)? |
|
Jan
7 |
|
accepted | Memory leak in a Java web application |
|
Jan
7 |
|
awarded | Nice Question |
|
Dec
8 |
|
awarded | Revival |
|
Dec
5 |
|
revised |
Apply a dynamic XPath expression when binding XML to ItemsSource updated code to be more concise, fit on screen without horizontal scrolling |
|
Dec
5 |
|
revised |
Memory leak in a Java web application added more data |
|
Dec
4 |
|
answered | Memory leak in a Java web application |
|
Dec
4 |
|
comment |
Memory leak in a Java web application I found this note in the documentation for Memory Analyzer that indicates that it might be "normal" GC behavior instead of a bug: "During the index creation, the Memory Analyzer removes unreachable objects because the various garbage collector algorithms tend to leave some garbage behind (if the object is too small, moving and re-assigning addresses is to expensive). This should, however, be no more than 3 to 4 percent." |
|
Nov
27 |
|
revised |
Memory leak in a Java web application added memory profile of tomcat server status application for comparison |
|
Nov
26 |
|
revised |
Memory leak in a Java web application counted the number of each unreachable string |
|
Nov
26 |
|
comment |
Memory leak in a Java web application I already used JVisualVM to obtain a heap dump, and Memory Analyzer indicates that the strings that are "leaking" are unreachable (i.e. nothing has a reference to them), and I can't find out what allocated them. |