Forum

Author Topic: Bad allocation  (Read 3528 times)

DenisIaq

  • Newbie
  • *
  • Posts: 8
    • View Profile
Bad allocation
« on: November 14, 2024, 04:01:05 PM »
Hello.

I am using Metashape Standard in Trial currently and i struggle to export cameras.

Its very strange because its only 61 images in 4k and i already did hundreds of images before with no error while exporting.

Here is the log file:

2024-11-14 13:57:32 Agisoft Metashape Standard Version: 2.1.3 build 18946 (64 bit)
2024-11-14 13:57:32 Platform: Windows
2024-11-14 13:57:32 CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (desktop)
2024-11-14 13:57:32 CPU family: 6 model: 158 signature: 906ECh
2024-11-14 13:57:32 RAM: 31.9 GB
2024-11-14 13:57:32 OpenGL Vendor: NVIDIA Corporation
2024-11-14 13:57:32 OpenGL Renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
2024-11-14 13:57:32 OpenGL Version: 4.6.0 NVIDIA 560.94
2024-11-14 13:57:32 Maximum Texture Size: 32768
2024-11-14 13:57:32 Quad Buffered Stereo: not enabled
2024-11-14 13:57:32 ARB_vertex_buffer_object: supported
2024-11-14 13:57:32 ARB_texture_non_power_of_two: supported
2024-11-14 13:57:38 LoadProject: path = Z:/Eos_fisheye_test/8mm/agisoft/agisoft.psz
2024-11-14 13:57:38 Loading project...
2024-11-14 13:57:39 loaded project in 1.081 sec
2024-11-14 13:57:39 Finished processing in 1.082 sec (exit code 1)
2024-11-14 13:57:54 ExportCameras: path = Z:/Eos_fisheye_test/15mm/export/colmap.txt, format = CamerasFormatColmap, crs = Local Coordinates (m), use_labels = on, binary = on
2024-11-14 13:57:54 Converting images...
2024-11-14 13:57:54 Cropped sensor calibration due to high distortion 4096x2160 -> 3965x2160
2024-11-14 13:57:54 Finished processing in 0.079 sec (exit code 0)
2024-11-14 13:57:54 Error: bad allocation

PolarNick

  • Full Member
  • ***
  • Posts: 109
    • View Profile
Re: Bad allocation
« Reply #1 on: November 19, 2024, 01:48:25 PM »
Hello!
Please share a project-reproducer to support@agisoft.com with steps to reproduce (probably open project + export cameras in colmap format?), so it was possible to reproduce and investigate the problem.
Probably small part of the project will be enough - just make sure that it can reproduce the problem.

vineg

  • Jr. Member
  • **
  • Posts: 68
    • View Profile
Re: Bad allocation
« Reply #2 on: November 20, 2024, 02:18:55 PM »
Hi!

High distortion handling was improved in 2.2.0 pre-release, please try to update from https://www.agisoft.com/forum/index.php?topic=16745.0
This error should not appear in that version.

Regards, Egor