Summary: | WebKit issue (cannot handle) -> kmail crashed at startup | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | omega <biasquez> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | biasquez, christophe, tokoe |
Priority: | NOR | ||
Version: | 2.0.89 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
email in mbox format New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
omega
2010-12-13 23:05:49 UTC
This crash is inside webkit's javascript engine, is this reproducible with a particular mail or any mail? (In reply to comment #1) > This crash is inside webkit's javascript engine, is this reproducible with a > particular mail or any mail? any mail Created attachment 55342 [details]
New crash information added by DrKonqi
kmail (2.0.89) on KDE Platform 4.5.90 (4.6 RC1) using Qt 4.7.1
- What I was doing when the application crashed:
after migration and reboot of my pc, sometimes kmail crashes at startup
-- Backtrace (Reduced):
#6 0x00007f9502e2e4b2 in JSC::ExecutableAllocator::isValid() const () from /usr/lib/libQtWebKit.so.4
#7 0x00007f9502e6f1f5 in JSC::JSGlobalData::JSGlobalData(JSC::JSGlobalData::GlobalDataType, JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#8 0x00007f9502e703f8 in JSC::JSGlobalData::createLeaked(JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#9 0x00007f95026b1872 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib/libQtWebKit.so.4
#10 0x00007f9502c1b7e6 in WebCore::FrameLoaderClientQt::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&) () from /usr/lib/libQtWebKit.so.4
Hej, can you reproduce it to 100% with a given email? If so, can you attach it here or send me via private mail? I have never seen such a crash before... Does it help to update Qt version? Ciao, Tobias (In reply to comment #4) > Hej, > > can you reproduce it to 100% with a given email? If so, can you attach it here > or send me via private mail? I have never seen such a crash before... > Does it help to update Qt version? > > Ciao, > Tobias i can reproduce this crash every time...this bug doesn't depend on any type of email. NOTE: - launching kmail first time -> kmail works fine - opening kmail, closing it and opening it again -> kmail crashed i have QT 4.7.1 (kubuntu natty version) about attachment, what do you prefer? (email, header, etc...) Complete email in mbox format, please. Created attachment 55492 [details]
email in mbox format
I'm inclined to mark this as either upstream or downstream. From the bt I get the impression that this is during startup (showing the "loading..." message) if so this should only happen if either the reporter or kubuntu changed that message into something that WebKit cannot handle (might have been an accidental change) or as a WebKit issue as it's their code that crashes. Omega: * Is this during startup or when displaying a message? * Does it occur on every startup (I get the impression that at first it wasn't but now it is)? * Is it reproducible using beta3 or newer? (In reply to comment #8) > I'm inclined to mark this as either upstream or downstream. > From the bt I get the impression that this is during startup (showing the > "loading..." message) if so this should only happen if either the reporter or > kubuntu changed that message into something that WebKit cannot handle (might > have been an accidental change) or as a WebKit issue as it's their code that > crashes. > > Omega: > * Is this during startup or when displaying a message? during startup > * Does it occur on every startup (I get the impression that at first it wasn't > but now it is)? - opening kmail, closing it and opening it again -> kmail crashed - launching kmail first time -> kmail works fine > * Is it reproducible using beta3 or newer? i'm using kde 4.6 rc1 and kde pim beta3 and by first time you mean after migration?(In reply to comment #9) > (In reply to comment #8) > > * Does it occur on every startup (I get the impression that at first it wasn't > > but now it is)? > - opening kmail, closing it and opening it again -> kmail crashed > - launching kmail first time -> kmail works fine after migration, or? (In reply to comment #10) > and by first time you mean after migration?(In reply to comment #9) > > (In reply to comment #8) > > > * Does it occur on every startup (I get the impression that at first it wasn't > > > but now it is)? > > - opening kmail, closing it and opening it again -> kmail crashed > > - launching kmail first time -> kmail works fine > > after migration, or? after migration *** Bug 261496 has been marked as a duplicate of this bug. *** Created attachment 56041 [details]
New crash information added by DrKonqi
kmail (2.0.89) on KDE Platform 4.5.95 (4.6 RC2) using Qt 4.7.1
- What I was doing when the application crashed:
(opening kmail, closing it and opening it again -> kmail crashed)
issue with kdepim 4.6 beta 4
-- Backtrace (Reduced):
#6 0x00007fd7438204b2 in JSC::ExecutableAllocator::isValid() const () from /usr/lib/libQtWebKit.so.4
#7 0x00007fd7438611f5 in JSC::JSGlobalData::JSGlobalData(JSC::JSGlobalData::GlobalDataType, JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#8 0x00007fd7438623f8 in JSC::JSGlobalData::createLeaked(JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#9 0x00007fd7430a3872 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib/libQtWebKit.so.4
#10 0x00007fd74360d7e6 in WebCore::FrameLoaderClientQt::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&) () from /usr/lib/libQtWebKit.so.4
topic changed Created attachment 56470 [details]
New crash information added by DrKonqi
kmail (2.0.89) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
- What I was doing when the application crashed:
new info reported after upgrade to kde 4.6.0
-- Backtrace (Reduced):
#6 0x00007f0c0e512642 in JSC::ExecutableAllocator::isValid() const () from /usr/lib/libQtWebKit.so.4
#7 0x00007f0c0e553615 in JSC::JSGlobalData::JSGlobalData(JSC::JSGlobalData::GlobalDataType, JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#8 0x00007f0c0e554838 in JSC::JSGlobalData::createLeaked(JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#9 0x00007f0c0dd93b12 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib/libQtWebKit.so.4
#10 0x00007f0c0e2ff9f6 in WebCore::FrameLoaderClientQt::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&) () from /usr/lib/libQtWebKit.so.4
UPDATE: when i have this issue, if i open kopete, then i can launch kmail without issue startup. Created attachment 57397 [details]
New crash information added by DrKonqi
kmail (2.0.89) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
UPDATE 2
with latest updates, when i have this issue, if i open kopete, then i can't launch kmail
-- Backtrace (Reduced):
#6 0x00007f5b047a6642 in JSC::ExecutableAllocator::isValid() const () from /usr/lib/libQtWebKit.so.4
#7 0x00007f5b047e7615 in JSC::JSGlobalData::JSGlobalData(JSC::JSGlobalData::GlobalDataType, JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#8 0x00007f5b047e8838 in JSC::JSGlobalData::createLeaked(JSC::ThreadStackType) () from /usr/lib/libQtWebKit.so.4
#9 0x00007f5b04027b12 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib/libQtWebKit.so.4
#10 0x00007f5b045939f6 in WebCore::FrameLoaderClientQt::createDocumentLoader(WebCore::ResourceRequest const&, WebCore::SubstituteData const&) () from /usr/lib/libQtWebKit.so.4
Just to check something, can you try that: sudo echo 1 > /proc/sys/vm/overcommit_memory then start KMail and see if it crashes (you may have to restart your KDE session, not sure about that) |