Six-Bit-TX commented 2 months ago

Windows Version

Microsoft Windows [version 10.0.22621.4037]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

The default version of colmap that comes with apt. Installable via

sudo apt install colmap

Nvidia driver, cuda

Repro Steps

prepare a folder of random images. run

colmap feature_extractor --image_path ${path to folder}

Expected Behavior

colmap create a database of features extracted form the images

Actual Behavior

Blackscreen, segfault.

Diagnostic Logs

No response

github-actions[bot] commented 2 months ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

Six-Bit-TX commented 1 month ago

D3D12: Removing Device. Aborted at 1726898377 (unix time) try "date -d @1726898377" if you are using GNU date PC: @ 0x0 (unknown) SIGSEGV (@0x28) received by PID 1455656 (TID 0x7f2ddf7ee640) from PID 40; stack trace: @ 0x7f2e1d3bf046 (unknown) @ 0x7f2e1b665520 (unknown) @ 0x7f2e152bc5ab (unknown) @ 0x7f2e14d51a43 (unknown) @ 0x7f2e148683c4 (unknown) @ 0x7f2e148693b6 (unknown) @ 0x7f2e148402c7 (unknown) @ 0x7f2e14842662 (unknown) @ 0x564b3ac64281 GLTexInput::SetImageData() @ 0x564b3ac56584 SiftGPU::RunSIFT() @ 0x564b3a85641d colmap::ExtractSiftFeaturesGPU() @ 0x564b3a8333e2 colmap::internal::SiftFeatureExtractorThread::Run() @ 0x564b3a915786 colmap::Thread::RunFunc() @ 0x7f2e1ba7b253 (unknown) @ 0x7f2e1b6b7ac3 (unknown) @ 0x7f2e1b749850 (unknown)

OneBlue commented 1 month ago

/logs

microsoft-github-policy-service[bot] commented 1 month ago

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!