VOGONS

Common searches


Search results

Display options

Re: Application eating >500MB of ram

Hello. Since this topic bumped up, I decided to reply. the last attached 'program' from ripsaw8080 really works. A month passed, computer has not been powered off - still no problem at all, no single memory leak or smth like that 😀 Thank you very much ripsaw8080! You saved my life! Jaroslav

Re: Application eating >500MB of ram

Well, it seems to me that the ~1MB of initial increase and tiny oscillation at the top is a bit nicer than the several hundred megabytes of oscillation with mass resetting of the search slots you'd normally get. The general idea might be a useful improvement for DOSBox as a patch; where the search …

Re: Application eating >500MB of ram

Hello again, just wanted to leave a note, that today nobody can let me in to test this solution.. so these tests must be left for tomorrow 🙁 And yes, the memory consumption is jumping from 48.868 MB to 48.528MB and so on. I'll be back with the results tomorrow I hope Jaroslav

Re: Applitacion eating >500MB of ram

Sorry, didn't notice the list problem. I guess the app needs the DTA filled even for individual file searches. I had an idea for a safer approach that calls FindNext after FindFirst for individual files (not wildcard searches). DOSBox closes the search slot and releases the memory when a search …

Re: Applitacion eating >500MB of ram

In order to stop (not just reduce) the memory consumption, I made a small TSR program that works like this: if the filespec being sought contains any wildcards, the search is passed on to DOSBox; but if it's an individual filename the TSR gets its attributes and uses success or failure to set the …

Re: Applitacion eating >500MB of ram

If it's some kind of drive cache problem, would running the program from a hard drive image instead of a mounted directory be a solution? Yes, the directory caching is not in effect for imgmounted drives. Jorpho and wd, thanks for your suggestions! maybe I could then somehow make an .iso from my …

Re: Applitacion eating >500MB of ram

- reimplement drive access without a drive cache - add lazy-style resolution switching - check regular runs with standard heap tracking tools (valgrind, purify etc.) thanks for suggestions, but first two suggestions sound to difficult for me... I will continue trying different dosbox configs etc …

Re: Applitacion eating >500MB of ram

so it's something to do with recompilation etc...? Recompiling without changing something is pretty useless. But yeah i can make an extensive list of things that you *may* fix in order to get rid of some possible memory leaks. Hello wd, I would be very thankful if you could make that list, when you …

Re: Applitacion eating >500MB of ram

May be the directory cache going crazy due to many open searches, or some playing with vga registers that change resolution but are not visible. Hello again :) 'directory cache' - I've searched a google about it, is it the: CTRL-F4 'Swap mounted disk-image (Only used with imgmount). Update …

Re: Applitacion eating >500MB of ram

A shot in the dark: Tried core=normal? Does the program switch the screen resolution frequently? Hello just tried your suggestion, but this won't help.. RAM usage goes from ~45 to 100mb in like 5 minutes... (I have also tried your's, MegaBuild v.5 - but same results) I have also tried all the types …

Application eating >500MB of ram

Hello everyone, I have used dosbox for so many times, but firstly I met the problem :( I have an old program, called SIMS II, it's a tool for security, it launches fine and works fine under DOSBOX, but I have problem with RAM. When I start DOSBOX, it eats ~45MB of ram. When I star a program SIMS, it …

Page 1 of 1