Opened 5 years ago

Closed 5 years ago

#3145 closed defect (can't reproduce)

File history unreadable

Reported by: chimerax-bug-report@… Owned by: Tom Goddard
Priority: normal Milestone:
Component: Input/Output Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description 

The following bug report has been submitted:
Platform:        Linux-3.10.0-1062.12.1.el7.x86_64-x86_64-with-centos-7.7.1908-Core
ChimeraX Version: 0.94 (2020-04-14)
Description
(Describe the actions that caused this problem to occur here)

Log:
Startup Errors  
---  
bug | The history of data files opened in ChimeraX was unreadable.  
The unreadable file has been copied to
/home/tanjiaxing/.local/share/ChimeraX/file_history.backup.20200505-224128.  
Please report this as a bug using menu Help / Report a Bug.  
  
The error was "Expecting value: line 1 column 1 (char 0)".  
  
UCSF ChimeraX version: 0.94.dev202004140658 (2020-04-14)  
© 2016-2020 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  




OpenGL version: 3.3.0 NVIDIA 418.43
OpenGL renderer: Quadro P4000/PCIe/SSE2
OpenGL vendor: NVIDIA Corporation
Manufacturer: Gigabyte Technology Co., Ltd.
Model: C246-WU4
OS: CentOS Linux 7 Core
Architecture: 64bit ELF
CPU: 8 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Cache Size: 12288 KB
Graphics:
	01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104GL [Quadro P4000] [10de:1bb1] (rev a1)
	Subsystem: NVIDIA Corporation Device [10de:11a3]
	Kernel driver in use: nvidia

Change History (2)

comment:1 by Eric Pettersen, 5 years ago

Component: Unassigned → Input/Output
Owner: set to Tom Goddard
Platform: → all
Project: → ChimeraX
Status: new → assigned
Summary: ChimeraX bug report submission → File history unreadable

comment:2 by Tom Goddard, 5 years ago

Resolution: → can't reproduce
Status: assigned → closed

Saw this once before. Not sure how file history JSON file gets corrupted. Possibly two running ChimeraX instances trying to write the file at the same time -- that is what the previous report looked like.

Note: See TracTickets for help on using tickets.