prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.69k stars 1.93k forks source link

Crash: ExtraRenderers.cpp(32): assert "variant.GetType() == "DataViewBitmapText"" #6339

Closed credomane closed 3 years ago

credomane commented 3 years ago

Version

PrusaSlicer-2.3.0

Operating system type + version

Manjaro

3D printer brand / version + firmware version (if known)

Ender 3 with SKR 1.4 Turbo running Marlin 2.0.7.1

Behavior

PrusaSlicer crashes.

ASSERT INFO: /build/prusa-slicer/src/PrusaSlicer-version_2.3.0/src/slic3r/GUI/ExtraRenderers.cpp(32): assert "variant.GetType() == "DataViewBitmapText"" failed in operator<<(). BACKTRACE: [1] wxDataViewRendererBase::FinishEditing() [2] wxDataViewRenderer::FinishEditing() [3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [5] wxEvtHandler::TryHereOnly(wxEvent&) [6] wxEvtHandler::ProcessEventLocally(wxEvent&) [7] wxEvtHandler::ProcessEvent(wxEvent&) [8] wxEvtHandler::SafelyProcessEvent(wxEvent&) [9] g_closure_invoke [10] g_signal_emit_valist [11] g_signal_emit [12] gtk_window_propagate_key_event [13] g_closure_invoke [14] g_signal_emit_valist [15] g_signal_emit [16] gtk_main_do_event [17] g_main_context_dispatch [18] g_main_loop_run [19] gtk_main [20] wxGUIEventLoop::DoRun() [21] wxEventLoopBase::Run() [22] wxAppConsoleBase::MainLoop() [23] wxEntry(int&, wchar_t**) [24] __libc_start_main

How to reproduce:

  1. Add a model to be sliced.
  2. Change the name of the model in the right panel to absolutely nothing. Make the name blank.
  3. Confirm the name change by clicking somewhere else in PrusaSlicer.
  4. Crash dialog appears.

Found this by total accident when trying to delete a model entirely.

lukasmatena commented 3 years ago

Thanks. Closing as a duplicate of https://github.com/prusa3d/PrusaSlicer/issues/2518. I assume that the AppImage from our buildserver does not suffer from this issue (let us know if it does).