Sudheer Satyanarayana wrote: > Hello, > > scid's UI freezes very often and has become unusable. > > I am using the version 4.5.2. > Using Tcl/Tk version: 8.5.14 > > Linux whibapom.lab.gavika.com <http://whibapom.lab.gavika.com> > 3.16.3-200.fc20.x86_64 #1 SMP Wed Sep 17 22:34:21 UTC 2014 x86_64 > x86_64 x86_64 GNU/Linux > > Fedora release 20 (Heisenbug) > > Steps to reproduce the issue; > 1. Launch scid > 2. Start engine 1 > 3. Play a few moves, either manually or using the Add Move button > 4. Click on the left arrow button to go back a move > 5. Click Add Move button > > This is not the only sequence that leads to UI freezing. > > Here's an excerpt from strace: > > select(4, [3], [], [], {0, 0}) = 0 (Timeout) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, > revents=POLLOUT}]) > writev(3, > [{"5\30\4\0001\31\0\2\31\t\0\2\17\0\373\1F\0\5\0001\31\0\2\4\0\0\2\0\0\0\0"..., > > 584}, {NULL, 0}, {"", 0}], 3) = 584 > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > select(4, [3], [], [], {0, 303}) = 0 (Timeout) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > select(4, [3], [], [], {0, 75}) = 0 (Timeout) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > read(6, 0x21c7288, 4096) = -1 EAGAIN (Resource > temporarily unavailable) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > select(7, [3 6], [], [], {0, 563886}) = 0 (Timeout) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > recvfrom(3, 0x185e5f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource > temporarily unavailable) > select(7, [3 6], [], [], NULL > > > Is there a way to workaround this? > Hi, thanks for the detailed report. By default Scid writes a log file named "engine1.log" tracing the input/output of the engine program (in the directory ~/.scid ). I think that Scid cannot write to that file and that is the cause of the freeze. You can try to rename or delete the ~/.scid directory to see if it will fix the problem. Bye, Fulvio
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
