VectorStyler
    • Categories
    • Unread
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Calling the Panel "Adjust Profile with Mask, could cause a Crash

    Scheduled Pinned Locked Moved Resolved Issues
    5 Posts 2 Posters 5.9k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      Subpath
      last edited by

      Calling the Panel "Adjust Profile with Mask" in the Stroke Width
      Panel Menu often leads to a crash of VS.

      unfortunately not reliably reproducible
      but it happens quite often

      setting preview could cause it
      or also just out of the blue

      when calling the panel there is sometime a small pause
      and then VS crashes

      Video about this

      Win 11
      CPU: AMD Ryzen 5 9600X, 6-core.
      GPU: Nvidia Geforce RTX 5070.

      VectorStylerV 2 Replies Last reply Reply Quote 1
      • VectorStylerV Offline
        VectorStyler @Subpath
        last edited by

        @Subpath Were there any crash reports on this one?
        I will try to replicate this.

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          Subpath @VectorStyler
          last edited by

          @VectorStyler

          yes there were crash reports, but sorry
          that were too many for me

          so i havent send any

          Win 11
          CPU: AMD Ryzen 5 9600X, 6-core.
          GPU: Nvidia Geforce RTX 5070.

          1 Reply Last reply Reply Quote 0
          • S Offline
            Subpath
            last edited by

            It seems to me that in this case
            there is a certain instability

            Win 11
            CPU: AMD Ryzen 5 9600X, 6-core.
            GPU: Nvidia Geforce RTX 5070.

            1 Reply Last reply Reply Quote 0
            • VectorStylerV Offline
              VectorStyler @Subpath
              last edited by

              @Subpath This issue should be fixed in build 1.1.062

              1 Reply Last reply Reply Quote 0
              • First post
                Last post