Summary: | R backend hangs using 100% when after trying to stop operation | ||
---|---|---|---|
Product: | [Applications] rkward | Reporter: | RKWard Team <rkward-devel> |
Component: | general | Assignee: | RKWard Team <rkward-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | All | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
RKWard Team
2013-04-10 09:55:40 UTC
- **labels**: --> NEEDINFO - Description has changed: Diff: ~~~~ --- old +++ new @@ -2,6 +2,7 @@ This is with RKWard 0.6.0z+0.6.1+pre1 on Fedora 18 64-bit. +~~~~~ rkward.rbackend: (gdb) t a a bt @@ -207,3 +208,4 @@ at kernel/qcoreapplication.cpp:1218 #9 0x00000000004356db in main (argc=<optimized out>, argv=0x7fff9b510c28) at /home/milan/Dev/rkward/rkward/rkward/main.cpp:194 +~~~~~ ~~~~ Hi! As usual, thanks for reporting! Whatever is going on, here, at the point of the backtrace, a SIGSEGV has been raised in the backend, and then we do a poor job at handling that. However, the root problem must have occurred some time earlier, and it is not directly visible in the backtrace. *Conceivably* this might be the same problem that I have fixed in trunk around a week ago (how would that be for coincidental timing?). On my machine this had different symptoms, but would also lead to a SIGSEGV when canceling a command under some conditions, also from RKRBackend::commandFinished() (thread 1, #16 in the backend's bt). Thus, please let me know, if you ever see this with a recent checkout from trunk (revision 4687 or later). Of course, if you do find a way to reproduce the problem, that would be useful, too. Can you give an estimate on how often you see this hang (percentage of canceled operations)? - **status**: open --> closed-out-of-date Closing for lack of feedback (and probably fixed). |