J jason Dec 12, 2003 #21 Chakolate said: jason wrote in What version are you running? When I was using 1.3 I got that problem all the time, but since I upgraded to 1.5, I get it hardly at all. Click to expand... I'm using 1.3. That's good to know they've fixed that problem.
Chakolate said: jason wrote in What version are you running? When I was using 1.3 I got that problem all the time, but since I upgraded to 1.5, I get it hardly at all. Click to expand... I'm using 1.3. That's good to know they've fixed that problem.
A Aaron Dec 12, 2003 #22 mozillazine has its own agenda. TAlk with the developers on the newsgroups and mailing lists directly and you'll get a more realistic picture. Click to expand... It was a developer that posted. Mozillazine guys just faithfully followed the advice. Aaron (my email is not munged!)
mozillazine has its own agenda. TAlk with the developers on the newsgroups and mailing lists directly and you'll get a more realistic picture. Click to expand... It was a developer that posted. Mozillazine guys just faithfully followed the advice. Aaron (my email is not munged!)
D donutbandit Dec 12, 2003 #23 It sounds like memory leaks. This is where ram is dynamically allocated and the author forgot to free it before normally exiting from the application. Click to expand... Don't know if it's memory leaks or not, but Firebird can take ages to recover from being minimized.
It sounds like memory leaks. This is where ram is dynamically allocated and the author forgot to free it before normally exiting from the application. Click to expand... Don't know if it's memory leaks or not, but Firebird can take ages to recover from being minimized.
