[kmail2] [Bug 372022] New: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.

[Jan-Matthias Braun]

https://bugs.kde.org/show_bug.cgi?id=372022

            Bug ID: 372022
           Summary: kmail2: message is displayed and blanked after short
                    delay. Mail actions then crash kmail2.
           Product: kmail2
           Version: 5.3.0
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: UI
          Assignee: kdepim-bugs at kde.org
          Reporter: jan_braun at gmx.net
  Target Milestone: ---

When selecting a mail in message view, the message is displayed and then
disappears after a variable delay. Changing to another mail and then back does
not triggering this behaviour. The disappearing message happens in the embedded
message view as well as in an extra window (after double clicking the message).

If the mail display is blank and I trigger any message related, e.g., reply,
forward, delete, kmail crashes. But if I redisplay the message and do the same
action while the display is intact, everything will work fine. Nonetheless,
this mail focuses on the disappearing of the displayed mail.

I see the following backtrace, which seems to lead into the depths of
QtWebEngine.

Received signal 11 SEGV_MAPERR 000000000008
#0 0x7ffff4cb3b3e base::debug::StackTrace::StackTrace()
#1 0x7ffff4cb3c2b base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7ffff22cc2b0 <unknown>
#3 0x7ffff33785b0
v8::internal::IncrementalMarking::ActivateIncrementalWriteBarrier()
#4 0x7ffff33787e7 v8::internal::IncrementalMarking::StartMarking()
#5 0x7ffff3378943 v8::internal::IncrementalMarking::Start()
#6 0x7ffff368ac9f v8::internal::MemoryReducer::TimerTask::RunInternal()
#7 0x7ffff4d46869 base::debug::TaskAnnotator::RunTask()
#8 0x7ffff541b323 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
#9 0x7ffff541bda0 scheduler::TaskQueueManager::DoWork()
#10 0x7ffff4d46869 base::debug::TaskAnnotator::RunTask()
#11 0x7ffff4cd79d5 base::MessageLoop::RunTask()
#12 0x7ffff4cd99ab base::MessageLoop::DoDelayedWork()
#13 0x7ffff4cdaaaf base::MessagePumpDefault::Run()
#14 0x7ffff4cefffd base::RunLoop::Run()
#15 0x7ffff4cd6f65 base::MessageLoop::Run()
#16 0x7ffff4a07baf content::RendererMain()
#17 0x7ffff3dc4cdb content::RunZygote()
#18 0x7ffff3dc5034 content::ContentMainRunnerImpl::Run()
#19 0x7ffff3dc34e1 content::ContentMain()
#20 0x7ffff311d514 QtWebEngine::processMain()
#21 0x000000400703 main
#22 0x7ffff22b9681 __libc_start_main
#23 0x000000400749 _start

What additional information can I provide?

Jan

-- 
You are receiving this mail because:
You are the assignee for the bug.