Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
NinjaLiquidator

SLADE3 Application Crash when Importing image

Recommended Posts

SLADE3 fails when I Import texture. Application crash. Please help.

Version: 3.1.0.5
Current action: arch_entry_import
Stack Trace:
0: (c:\dev\slade3\src\archivepanel.cpp:1472) ArchivePanel::importEntry
1: (c:\dev\slade3\src\archivepanel.cpp:2868) ArchivePanel::handleAction
2: (c:\dev\slade3\src\mainapp.cpp:1111) MainApp::doAction
3: (c:\dev\slade3\src\mainapp.cpp:1183) MainApp::onMenu
4: (f:\programming\libs\wxwidgets-3.0.2\src\common\appbase.cpp:612) wxAppConsoleBase::HandleEvent
5: (f:\programming\libs\wxwidgets-3.0.2\src\common\appbase.cpp:623) wxAppConsoleBase::CallEventHandler
6: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1751) wxEvtHandler::SearchDynamicEventTable
7: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1585) wxEvtHandler::TryHereOnly
8: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1495) wxEvtHandler::ProcessEvent
9: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1416) wxEvtHandler::DoTryApp
10: (f:\programming\libs\wxwidgets-3.0.2\src\common\wincmn.cpp:3433) wxWindowBase::TryAfter
11: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1508) wxEvtHandler::ProcessEvent
12: (f:\programming\libs\wxwidgets-3.0.2\src\common\wincmn.cpp:3427) wxWindowBase::TryAfter
13: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1508) wxEvtHandler::ProcessEvent
14: (f:\programming\libs\wxwidgets-3.0.2\src\common\event.cpp:1647) wxEvtHandler::SafelyProcessEvent
15: (f:\programming\libs\wxwidgets-3.0.2\src\common\menucmn.cpp:666) wxMenuBase::SendEvent
16: (f:\programming\libs\wxwidgets-3.0.2\src\common\framecmn.cpp:298) wxFrameBase::ProcessCommand
17: (f:\programming\libs\wxwidgets-3.0.2\src\msw\frame.cpp:826) wxFrame::HandleCommand
18: (f:\programming\libs\wxwidgets-3.0.2\src\msw\frame.cpp:889) wxFrame::MSWWindowProc
19: (f:\programming\libs\wxwidgets-3.0.2\src\msw\window.cpp:2711) wxWndProc
20: [unknown location] gapfnScSendMessage
21: [unknown location] gapfnScSendMessage
22: [unknown location] GetKeyboardLayout
23: [unknown location] DispatchMessageW
24: (f:\programming\libs\wxwidgets-3.0.2\src\msw\evtloop.cpp:170) wxGUIEventLoop::ProcessMessage
25: (f:\programming\libs\wxwidgets-3.0.2\src\msw\evtloop.cpp:232) wxGUIEventLoop::Dispatch
26: (f:\programming\libs\wxwidgets-3.0.2\src\common\evtloopcmn.cpp:206) wxEventLoopManual::DoRun
27: (f:\programming\libs\wxwidgets-3.0.2\src\common\evtloopcmn.cpp:78) wxEventLoopBase::Run
28: (f:\programming\libs\wxwidgets-3.0.2\src\common\appbase.cpp:334) wxAppConsoleBase::MainLoop
29: (f:\programming\libs\wxwidgets-3.0.2\src\common\init.cpp:495) wxEntryReal
30: (f:\programming\libs\wxwidgets-3.0.2\src\msw\main.cpp:188) wxEntry
31: (f:\programming\libs\wxwidgets-3.0.2\src\msw\main.cpp:415) wxEntry
32: (c:\dev\slade3\src\mainapp.cpp:306) WinMain
33: (f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618) __tmainCRTStartup
34: [unknown location] BaseThreadInitThunk
35: [unknown location] RtlInitializeExceptionChain
36: [unknown location] RtlInitializeExceptionChain

Share this post


Link to post
SavageCorona said:

You really didn't need to do that.

Programmers prefer a thread per issue, at least in bugtrackers and the such. Forum rules have different etiquette perhaps. There's a better place to report SLADE bugs anyway, on the github project for it.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
×