-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Closed
Labels
bugA problem with current functionality, as opposed to missing functionality (enhancement)A problem with current functionality, as opposed to missing functionality (enhancement)frozen-due-to-ageIssues closed and untouched for a long time, together with being locked for discussionIssues closed and untouched for a long time, together with being locked for discussionnot-our-bugUsed only when we want to keep an issue open for visibility, but the real problem is somewhere elseUsed only when we want to keep an issue open for visibility, but the real problem is somewhere else
Milestone
Description
The panic error name looks the same as #7005, but the content seems to differ, so I am submitting a new issue. If the two are related to the same problem, please close this one and use the other one instead.
The panic happened without any user intervention. Syncthing had just been doing its job, and I only found the log file later.
The log comes from Syncthing v1.10.0 (x86-32) running in Windows 10 Enterprise 2016 LTSB x86.
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0xbe295e]
goroutine 184 [running]:
github.com/syncthing/notify.(*readdcw).loopevent(0x12c881e0, 0x62, 0x139f7880)
github.com/syncthing/notify@v0.0.0-20190709140112-69c7a957d3e2/watcher_readdcw.go:400 +0x3e
github.com/syncthing/notify.(*readdcw).loop(0x12c881e0)
github.com/syncthing/notify@v0.0.0-20190709140112-69c7a957d3e2/watcher_readdcw.go:362 +0xb7
created by github.com/syncthing/notify.(*readdcw).lazyinit
github.com/syncthing/notify@v0.0.0-20190709140112-69c7a957d3e2/watcher_readdcw.go:335 +0xa2
Metadata
Metadata
Assignees
Labels
bugA problem with current functionality, as opposed to missing functionality (enhancement)A problem with current functionality, as opposed to missing functionality (enhancement)frozen-due-to-ageIssues closed and untouched for a long time, together with being locked for discussionIssues closed and untouched for a long time, together with being locked for discussionnot-our-bugUsed only when we want to keep an issue open for visibility, but the real problem is somewhere elseUsed only when we want to keep an issue open for visibility, but the real problem is somewhere else