Il 21/08/2013 16:56, jeremy rosen ha scritto: > This crash has been reported multiple times, but so far no clear explanation > has been given on the mailing list > > > Mainly because we didn't know exactly what was going on. > > So, for all people that had some mysterious crash on import in the last couple of days... here are a few pointers > > > HOW TO SEE IF YOUR CRASH IS THE SAME AS THIS ONE > The thread that dies will be in one of the backgroundjobs function (might be a couple of frames up the stack) > > > HOW TO GET RID OF THE CRASH > update trunk, trunk shouldn't crash on this since yesterday evening > > * commit f359b2d79b4 disables lua which triggers the bug > * commit 4b539ee0b158d40 fixes the bug but needs more testing > > > HOW TO HELP ME TEST THE FIX > > * you need to have a reliable way to trigger the bug > * reenable lua on your local build by uncommenting the two lua sections in src/CMakelist.txt > * try to trigger the bug and see if it disapears > > > > hope this helps >
Hi jeremy, I join this thread because I have the same problem and I updated redmine report few days ago (Bug #9552). I'm trying to follow your instructions but I have some problems. When you say "trunk" do you mean git master branch? I git-pulled now but I can't find the commits you describe :( The current git master still crashing when I import a folder. Thanks! Ivan ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
