L5 Mac Crash: Typing in search box in library window
I started to type to search for an author in the library drop down window (i.e. author:Moore) and Logos 5 Mac crashed. No Apple error log or anything. I have logged this crash once before and did not receive any kind of response on it. Anyhow, here are logs once again. I am running OSX 10.8.2 and L5.0a SR-3.
Comments
-
Donovan, it's the "Too many open files" problem that is reported as being worked on.
Dave
===Windows 11 & Android 13
0 -
That's wild because I think I only had two resources open at the time! (DMBI and COD). I also had only be using Logos for about two hours and I had freshly booted up, so the memory should have been cleared.
All this to say, Logos 5 Mac has got a real issue memory management wise.
0 -
"Files" don't necessarily mean open resources. Your search parameters will execute upon a number of "files". Honestly Martin can explain this better than I can, but the way I understand it all of the intricacies in the search call upon and open different files, so the more complicated the search is, and/or the more layers of filtration that are on the resources being searched, the more files that are being opened.
0 -
Tommy Ball said:
"Files" don't necessarily mean open resources. Your search parameters will execute upon a number of "files".
No matter how it is caused, when can we expect a fix? We also have problems with memory leakage, which should not happen
0 -
It is a physical limitation within the OS as I understand it. It didn't happen as much with Logos 4 because the version of Cocoa Logos 4 was using. It wasn't able to do as much at one time as Logos 5 is. I reached out to Martin to see if he could give me some clear word on the matter to pass on, or to post here himself.
0 -
Donovan R. Palmer said:
That's wild because I think I only had two resources open at the time! (DMBI and COD).
Which is why your log should be closely examined. After generating a Home page several panels were opened and then you closed them all. There were a large number of duplicate searches of the library catalog index e.g. LibraryCatalogIndex | Searching for all records matching: mytag:bestcom, lots of sync'ing and finally it crashed after you tried a search for author:M (Moore!).
Were all (internal) files closed ASAP or left open?
Dave
===Windows 11 & Android 13
0 -
Tommy Ball said:
It is a physical limitation within the OS as I understand it. It didn't happen as much with Logos 4 because the version of Cocoa Logos 4 was using. It wasn't able to do as much at one time as Logos 5 is. I reached out to Martin to see if he could give me some clear word on the matter to pass on, or to post here himself.
Mac OS X has a system wide kernel limitation for open files (e.g. 12,288) and a per process limit for open files (e.g. 256). Wonder if Logos 5 could be modified to include:
ulimit -n 512during program initialization to increase per process user limit from 256 to 512 ?
To display system wide max files:
sysctl kern.maxfilesKeep Smiling [:)]
0 -
Mac OS X has a system wide kernel limitation for open files (e.g. 12,288) and a per process limit for open files (e.g. 256). Wonder if Logos 5 could be modified to include:
ulimit -n 512Using Process Explorer (Windows) I counted open file handles:-
615 on startup
630 after 3m doing nothing
655 after doing some work, incl searches
584 after closing all panels (15)
Almost all databases had 2 handles
Almost all resources had multiple handles:-
7 if in Guides or Parallel Resources or Prioritised**
10 if in panels (16 if searched)
** ones used by the program.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Which is why your log should be closely examined. After generating a Home page several panels were opened and then you closed them all. There were a large number of duplicate searches of the library catalog index e.g. LibraryCatalogIndex | Searching for all records matching: mytag:bestcom, lots of sync'ing and finally it crashed after you tried a search for author:M (Moore!).
My studies were very focused and only involved two or three resources. It is interesting about the search for 'my tag:bestcom', because I did not search using this parameter. In fact, I didn't do a lot of searching... mainly just lookup of terms. This leads me to believe that Logos is doing stuff under the hood that I am not aware of which is resulting in this overrun of files. Something is not right... Houston, we got a problem.
0
said: