Out of Memory Error: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 11: | Line 11: | ||
Clicking help just gives a gray screen. | Clicking help just gives a gray screen. | ||
== Further troubleshooting == | |||
=== When does the error happen? === | |||
I can replicate the error (i.e. make it happen consistently) by opening and closing patients about 30 times. The error has also happened when adding a new patient. | |||
{discussion} | |||
* Does anyone know of another '''replicable''' way of making this error happen consistently? Knowing how to trigger this might help me eliminate the error. [[User:Ttenbergen|Ttenbergen]] 10:01, 5 April 2011 (CDT) | |||
== Details == | |||
I am able to reproduce the error if I manually open and close pts from patientlist pick button and view form door button. I wrote a test program to see if I can force the error programmatically; the program opens and closes patients 100 times, but this doesn't trigger a problem. | I am able to reproduce the error if I manually open and close pts from patientlist pick button and view form door button. I wrote a test program to see if I can force the error programmatically; the program opens and closes patients 100 times, but this doesn't trigger a problem. | ||
The error does not happen if I just open and close the patient viewer directly, i.e. not from Patientlist. | |||
The error seems to happen upon the doCmd.Openform in sub cb_pick_click. | |||
There was a theory that this is related to '''battery power vs. mains power'''; I replicated the error on my PC, so I really doubt it has anything to do with that. | There was a theory that this is related to '''battery power vs. mains power'''; I replicated the error on my PC, so I really doubt it has anything to do with that. | ||
It sounds like most people have had this error at times, and it seems to be more prevalent at high throughput locations. | |||
When the error happens, task manager looks like the memory is not the problem, but CPU load spikes. | |||
Restarting CCMDB.mdb "fixes" the problem, but that's not a solution. | |||
[[Category:Bugs]] | [[Category:Bugs]] | ||