Skip to content

Crash on negative trim end #17

Closed
Closed

Description

@mspnr

If trim end is negative the app is crashing:

Rive_-_Google_Chrome_chrome_JrNX4WeS2W

Rive_-_Google_Chrome_chrome_TjqSAbJqMQ

A: ../src/shapes/metrics_path.cpp:284: void rive::MetricsPath::extractSubPart(int, float, float, bool, rive::RenderPath *): assertion "startT >= 0.0f && startT <= 1.0f && endT >= 0.0f && endT <= 1.0f" failed
A: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 14135 (runtime.example), pid 14135 (runtime.example)

Activity

  1. mjtalbot commented on Mar 19, 2021

    @mjtalbot
    Contributor

    thank you for reporting this bug! we'll get this repro'd and fixed up

  2. mjtalbot commented on Apr 7, 2021

    @mjtalbot
    Contributor

    this is fixed as part of moving to format7 #24. You will need to re export your files as format7 to take advantage of this. Also you can now no longer enter negative trim start/ end (offset still can be negative however).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions