| Summary: | tellico 3.0.2 crashes on save with or without images in data file | ||
|---|---|---|---|
| Product: | [Applications] tellico | Reporter: | goupilcom <goupilcom> |
| Component: | general | Assignee: | Robby Stephenson <robby> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 3.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/tellico/1a828b340ca72b18f04c05a95422f741fffe502a | Version Fixed In: | 3.1 |
| Attachments: |
The complete messages on console of Tellico 3.0.2 when it crash
The same operation with gdb tellico (+bt) |
||
|
Description
goupilcom@gmail.com
2017-06-04 17:23:14 UTC
Thanks for the report. I haven't been able to reproduce the crash myself yet, but the size of your database file does make it a good one to use for performance improvements, too. Are you compiling from source? Your backtrace doesn't include any of Tellico's symbol which might be helpful. Using CMAKE_BUILD_TYPE=debugfull in your compile would do it - or maybe your distribution has debug package for Tellico? Thanks Git commit 1a828b340ca72b18f04c05a95422f741fffe502a by Robby Stephenson. Committed on 03/07/2017 at 00:56. Pushed by rstephenson into branch 'master'. Split very large XML files into chunks when writing to QTextStream I could reproduce the crash in Bug 380832 when writing an XML file aroud 500 MB. Splitting the writing into 100 MB chunks fixed my crash. I don't know how to pick the best chunk size or how to properly catch an out of memory (bad_alloc) exception which seems to happen. I could reproduce the bug in Tellico 2.3.12, so that seems like a bit different experience than the bug reporter. Also, as a To DO item, Tellico should switch to using QXmlStreamWriter instead of QDomDcument::toString() for these big files, especially. FIXED-IN: 3.1 M +1 -0 ChangeLog M +10 -3 src/core/filehandler.cpp https://commits.kde.org/tellico/1a828b340ca72b18f04c05a95422f741fffe502a Created attachment 106470 [details]
The complete messages on console of Tellico 3.0.2 when it crash
The complete messages on console of Tellico 3.0.2 when it crash
The messages on console when it crash with Tellico 3.0.2 compiled with the option $ make -j8 CMAKE_BUILD_TYPE=debugfull (In reply to Robby Stephenson from comment #2) > Are you compiling from source? Your backtrace doesn't include any of > Tellico's symbol which might be helpful. Using CMAKE_BUILD_TYPE=debugfull in > your compile would do it - or maybe your distribution has debug package for > Tellico? Thanks I had compiling Tellico 3.0.2 another time with the option : CMAKE_BUILD_TYPE=debugfull cmake . -DCMAKE_BUILD_TYPE=debugfull make -j8 I have lauched Tellico : $ ./tellico Then i have only modified a date (a year) on a record and saved the record (no crash) then i have saved the data base. As the last time, Tellico crash at 80%. And i have joined the result on the attach file above (In reply to Robby Stephenson from comment #3) > Git commit 1a828b340ca72b18f04c05a95422f741fffe502a by Robby Stephenson. > Committed on 03/07/2017 at 00:56. > Pushed by rstephenson into branch 'master'. > > Split very large XML files into chunks when writing to QTextStream > > I could reproduce the crash in Bug 380832 when writing an XML file > aroud 500 MB. Splitting the writing into 100 MB chunks fixed my crash. > I don't know how to pick the best chunk size or how to properly catch > an out of memory (bad_alloc) exception which seems to happen. > > I could reproduce the bug in Tellico 2.3.12, so that seems like a bit > different experience than the bug reporter. > > Also, as a To DO item, Tellico should switch to using QXmlStreamWriter > instead of QDomDcument::toString() for these big files, especially. > FIXED-IN: 3.1 > > M +1 -0 ChangeLog > M +10 -3 src/core/filehandler.cpp > > https://commits.kde.org/tellico/1a828b340ca72b18f04c05a95422f741fffe502a Thank you very much Created attachment 106471 [details]
The same operation with gdb tellico (+bt)
|