Crash on startup, 4.2a beta4
I got a crash after the program started...I suspect it was when it was loading the default layout. I tried starting without a layout and it started fine, but when I loaded the last layout, it crashed again.
I will try other things later when I have time.
First crash after startup:
2158.Copy-_2800_2_2900_-of-Logos4.log
Crash when loading layout:
MacBook Pro (2019), ThinkPad E540
Comments
-
I'll submit your logs to development. Were the layouts the same? Do you recall what panels were included?
0 -
One of the errors you're getting is ERROR_NO_SYSTEM_RESOURCES (Insufficient system resources exist to complete the requested service.)
What OS are you running, how much RAM do you have, and how long has it been since you last rebooted? If you reboot your OS, does the problem still occur?
0 -
It was a resource problem, although I'm not sure what--I had about 1 GB of free RAM when I was trying this (out of a total of 3GB) . Perhaps memory was fragmented in a strange way. Anyhow I shutdown Firefox, and I was able to run Logos without a crash, and then I started Firefox back up, and everything is running fine again. I'm running XP, FWIW.
MacBook Pro (2019), ThinkPad E540
0 -
The "insufficient system resources" message is typically not related to available RAM, but usually is caused by running out of certain OS kernel objects. The system allocates space for a fixed number of these (usually based on total system RAM) at boot and they're shared among all running processes. If Firefox was leaking handles, for example, restarting it would have freed them all (when the old process exited), letting Logos 4 acquire the resources it needed. That's the ideal situation; in the worst case, a system driver is leaking handles, and you can't free them without rebooting the system.
0 -
Bradley Grainger said:
The "insufficient system resources" message is typically not related to available RAM, but usually is caused by running out of certain OS kernel objects. The system allocates space for a fixed number of these (usually based on total system RAM) at boot and they're shared among all running processes. If Firefox was leaking handles, for example, restarting it would have freed them all (when the old process exited), letting Logos 4 acquire the resources it needed. That's the ideal situation; in the worst case, a system driver is leaking handles, and you can't free them without rebooting the system.
Firefox is the leaker I think. Its memory footprint steadily grows over time. If I let it go too long it will take upwards of 600-800 MB. Especially when I'm visiting sites that have a lot of Flash or Silverlight.
MacBook Pro (2019), ThinkPad E540
0
