Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building on Linux: assert "uiIndex < m_nCount" failed in Item() #6421

Closed
gringer opened this issue Apr 23, 2021 · 5 comments
Closed

Building on Linux: assert "uiIndex < m_nCount" failed in Item() #6421

gringer opened this issue Apr 23, 2021 · 5 comments
Labels
Build Build issues

Comments

@gringer
Copy link

gringer commented Apr 23, 2021

Version

version_2.4.0-alpha0-194-g657d19482

Operating system type + version

Debian frankenLinux: sid / bullseye / buster

$ uname -a
Linux elegans 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux

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

N/A. I'm only testing out the UI.

Behavior

Directly after showing the splash screen (i.e. after running prusa-slicer from the command line), this happens:

ASSERT INFO:
../include/wx/dynarray.h(838): assert "uiIndex < m_nCount" failed in Item().

BACKTRACE:
[1] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[2] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[3] wxEvtHandler::TryHereOnly(wxEvent&)
[4] wxEvtHandler::ProcessEventLocally(wxEvent&)
[5] wxEvtHandler::ProcessEvent(wxEvent&)
[6] wxNotebookBase::SendPageChangedEvent(int, int)
[7] g_closure_invoke
[8] g_signal_emit_valist
[9] g_signal_emit
[10] wxNotebook::InsertPage(unsigned long, wxWindow*, wxString const&, bool, int)
[11] wxEntry(int&, wchar_t**)
[12] __libc_start_main

I have the option of Stop or Continue. Clicking Continue leads directly to a segmentation fault.

  • Expected Results

    • Seeing a user interface
  • Actual Results

    • Kicked out of the application
      prusa
@rtyr rtyr added the Build Build issues label Apr 23, 2021
@gringer
Copy link
Author

gringer commented Apr 23, 2021

I tried compiling using cmake -DSLIC3R_STATIC=1 .., and got the following pre-compilation error:

CMake Error at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  TBB library cannot be found.  Consider set TBBROOT environment variable.
  (missing: TBB_LIBRARIES) (found version "2020.3")

Without that flag, it passes the TBB section (but leads to the above error):

-- Found TBB: /usr/include (found version "2020.3")  
--   TBB_FOUND               = TRUE
--   TBB_INCLUDE_DIRS        = /usr/include
--   TBB_DEFINITIONS         = 
--   TBB_LIBRARIES           = /usr/lib/x86_64-linux-gnu/libtbb.so
--   TBB_DEFINITIONS_DEBUG   = TBB_USE_DEBUG=1
--   TBB_LIBRARIES_DEBUG     = 
--   TBB_DEFINITIONS_RELEASE = 
--   TBB_LIBRARIES_RELEASE   = /usr/lib/x86_64-linux-gnu/libtbb.so

This [also] happens on another frankenDebian computer I'm using:

$ uname -a
Linux hera 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1 (2021-03-27) x86_64 GNU/Linux

@gringer
Copy link
Author

gringer commented Apr 24, 2021

I've been able to get it to compile with static libraries by pre-compiling the deps directory:

cd deps/
mkdir build; cd build
cmake .. -DDESTDIR=/home/${USER}/install/PS
make
cd ..
mkdir build; cd build
cmake -DSLIC3R_STATIC=1 -DCMAKE_PREFIX_PATH=/home/${USER}/install/PS/usr/local ..
make

This seems to be working...

PrusaSlic3r

@Kristaba
Copy link

Same issue on Arch Linux, when building master branch.
I will try building the version_2.4.0-alpha0 tag just in case, and build with static libraries if it still fails as proposed by @gringer .

$ uname -a
Linux archlinux 5.11.14-arch1-1 #1 SMP PREEMPT Wed, 14 Apr 2021 12:06:34 +0000 x86_64 GNU/Linux

I am not familiar with PrusaSlicer code nor wxWidgets, but if someone has a few pointers or a patch to test, I can probably manage to find some time.

@Kristaba
Copy link

I missed the discussion on the Arch AUR thread, which links back to another issue here. As it refers to the same problem, either this one or #6270 should be marked as duplicated.

@gringer gringer closed this as completed May 6, 2021
@gringer
Copy link
Author

gringer commented May 6, 2021

This issue is a duplicate of #6270

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Build issues
Projects
None yet
Development

No branches or pull requests

3 participants