benchmark-cli panics on Windows and Linux #73627

New Issue

Paul Graydon · 2020-02-06T06:50:10+01:00

Paul Graydon commented

2020-02-06 06:50:10 +01:00

System Information
Operating system: Windows 10, Windows 2012 R2 Standard. Oracle Linux 7, Ubuntu 18.04
Graphics card: Various, seems irrelevant.

Blender Version
Broken: benchmark-launcher-cli version 2.0.4

Short description of error
benchmark CLI works in interactive mode, but if run via CLI arguments, it throws an error every time. Seems to be the same error on both Windows and Linux

Exact steps for others to reproduce the error

Download the relevant (current) version of the benchmark-launcher-cli and extract.
Try to start the benchmark via the benchmark sub command and watch as it panics.

Windows:

> .\benchmark-launcher-cli.exe benchmark

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x1 addr=0x0 pc=0x51af85]

goroutine 1 [running]:
sync.(*Mutex).Lock(...)
        c:/go/src/sync/mutex.go:74
log.(*Logger).Output(0x0, 0x2, 0xc00001a960, 0x2b, 0x0, 0x0)
        c:/go/src/log/log.go:153 +0x75
log.(*Logger).Printf(0x0, 0x9f46aa, 0x2, 0xc000099f10, 0x1, 0x1)
        c:/go/src/log/log.go:179 +0x85
git.blender.org/blender-open-data/launcher/internal.ExitWithError(0xab2360, 0xc0000518a0)
        C:/msys64/home/sem/git/blender-open-data/launcher/internal/application.go:9 +0xb3
main.main()
        C:/msys64/home/sem/git/blender-open-data/launcher/cmd/benchmark-launcher-cli/main.go:14 +0x63

Ubuntu (entirely different machine):

]$ ./benchmark-launcher-cli benchmark
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x503ace]

goroutine 1 [running]:
sync.(*Mutex).Lock(...)
        /usr/local/go/src/sync/mutex.go:74
log.(*Logger).Output(0x0, 0x2, 0xc00009c630, 0x2b, 0x0, 0x0)
        /usr/local/go/src/log/log.go:153 +0x6e
log.(*Logger).Printf(0x0, 0x9a80cb, 0x2, 0xc0000bff10, 0x1, 0x1)
        /usr/local/go/src/log/log.go:179 +0x7e
git.blender.org/blender-open-data/launcher/internal.ExitWithError(0xa68fc0, 0xc00008b950)
        /repo/launcher/internal/application.go:9 +0xac
main.main()
        /repo/launcher/cmd/benchmark-launcher-cli/main.go:14 +0x5c

Seems to be the same underlying issue?

Based on the default startup or an attached .blend file (as simple as possible).

Note: I've yet to test on OSX, I can give it a shot tomorrow, but given Windows and Linux seems to be the same issue, I'm assuming it'll be identical there.

**System Information** Operating system: Windows 10, Windows 2012 R2 Standard. Oracle Linux 7, Ubuntu 18.04 Graphics card: Various, seems irrelevant. **Blender Version** Broken: benchmark-launcher-cli version 2.0.4 **Short description of error** benchmark CLI works in interactive mode, but if run via CLI arguments, it throws an error every time. Seems to be the same error on both Windows and Linux **Exact steps for others to reproduce the error** * Download the relevant (current) version of the benchmark-launcher-cli and extract. * Try to start the benchmark via the benchmark sub command and watch as it panics. Windows: ``` > .\benchmark-launcher-cli.exe benchmark panic: runtime error: invalid memory address or nil pointer dereference [signal 0xc0000005 code=0x1 addr=0x0 pc=0x51af85] goroutine 1 [running]: sync.(*Mutex).Lock(...) c:/go/src/sync/mutex.go:74 log.(*Logger).Output(0x0, 0x2, 0xc00001a960, 0x2b, 0x0, 0x0) c:/go/src/log/log.go:153 +0x75 log.(*Logger).Printf(0x0, 0x9f46aa, 0x2, 0xc000099f10, 0x1, 0x1) c:/go/src/log/log.go:179 +0x85 git.blender.org/blender-open-data/launcher/internal.ExitWithError(0xab2360, 0xc0000518a0) C:/msys64/home/sem/git/blender-open-data/launcher/internal/application.go:9 +0xb3 main.main() C:/msys64/home/sem/git/blender-open-data/launcher/cmd/benchmark-launcher-cli/main.go:14 +0x63 ``` Ubuntu (entirely different machine): ``` ]$ ./benchmark-launcher-cli benchmark panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x503ace] goroutine 1 [running]: sync.(*Mutex).Lock(...) /usr/local/go/src/sync/mutex.go:74 log.(*Logger).Output(0x0, 0x2, 0xc00009c630, 0x2b, 0x0, 0x0) /usr/local/go/src/log/log.go:153 +0x6e log.(*Logger).Printf(0x0, 0x9a80cb, 0x2, 0xc0000bff10, 0x1, 0x1) /usr/local/go/src/log/log.go:179 +0x7e git.blender.org/blender-open-data/launcher/internal.ExitWithError(0xa68fc0, 0xc00008b950) /repo/launcher/internal/application.go:9 +0xac main.main() /repo/launcher/cmd/benchmark-launcher-cli/main.go:14 +0x5c ``` Seems to be the same underlying issue? Based on the default startup or an attached .blend file (as simple as possible). Note: I've yet to test on OSX, I can give it a shot tomorrow, but given Windows and Linux seems to be the same issue, I'm assuming it'll be identical there.

Paul Graydon commented

2020-02-06 06:50:10 +01:00

Added subscriber: @Twirrim