Skip to content

Error Codes & Troubleshooting

Jump to bottom
Tharun Birla edited this page Jun 13, 2026 · 1 revision

If LibreCuts encounters a critical problem during frame rendering or file management, an error dialog will pop up displaying a unique application code. Below is the comprehensive master list of all LC- error codes, what they mean, and how to fix them.

Master Error Code Reference

LC-101: FFMPEG_EXECUTION_FAILED

  • Description: FFmpeg failed to process the video.
  • Cause: This usually occurs if the source video codec is completely unsupported or if you are running out of storage space middle of the render.
  • Troubleshooting: Try processing a shorter clip or verifying that the input video isn't corrupted.

LC-102: FONT_MISSING

  • Description: Font file could not be loaded from assets.
  • Cause: The application failed to index required layout typeface items from the local build folder.
  • Troubleshooting: Recompile the application and ensure asset paths are untouched.

LC-201: FILE_NOT_FOUND

  • Description: Source video file is missing or inaccessible.
  • Cause: The source file was either moved, deleted, or the application was not granted appropriate storage permissions by Android.
  • Troubleshooting: Make sure you haven't deleted the source video from your device gallery before exporting, and check app storage permissions under Settings.

LC-202: GALLERY_SAVE_FAILED

  • Description: Could not save the processed video to the gallery.
  • Cause: System write failure or insufficient media directory authorizations.
  • Troubleshooting: Clear up disk space on your local storage and ensure LibreCuts has permissions to write to media galleries.

LC-301: OUT_OF_MEMORY

  • Description: The app ran out of memory while processing frames.
  • Cause: The video timeline is too intensive or high-resolution processing overwhelmed the execution memory.
  • Troubleshooting: Close other heavy background apps and try compiling the video again.

LC-500: UNEXPECTED_CRASH

  • Description: An unexpected application error occurred.
  • Cause: General fallback code for global unexpected app crashes.
  • Troubleshooting: Read the internal application log via the crash reporter window.

How to Report a Bug

When the app encounters an issue, a customized interface overlay will appear. Follow these steps to help patch it:

  1. Copy the Log: Tap the "Copy Log" option inside the dialog wrapper. This saves the error dump details safely onto your system clipboard.
  2. Open GitHub Issues: Tap "GitHub Report". The application will automatically attempt to open a browser tracking line populated with contextual repository parameters.
  3. Submit: Paste your clipboard data right into the issue body context and submit it to the core repository timeline!

Clone this wiki locally