Closed
Bug 144428
Opened 23 years ago
Closed 23 years ago
[Qt] Qt-Mozilla hangs in nsASingleFragmentCString::GetReadableFragment (?) on startup, before bringing up the UI.
Categories
(Core Graveyard :: GFX, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bero, Assigned: roland.mainz)
References
Details
(Whiteboard: [whitebox])
Attachments
(1 file, 1 obsolete file)
2.03 KB,
patch
|
Biesinger
:
review+
|
Details | Diff | Splinter Review |
Last output (stderr):
GFX: dpi=75 t2p=0.0526316 p2t=19 depth=16
JCG: eBorderStyle_close isn't handled yet... please fix me
Correction: It doesn't crash, it just hangs forever after displaying the
eBorderStyle_close message.
My first guess is it waits for user input without bothering to show the dialog
it's waiting for first, probably it forgets to enter the Qt event loop.
Last couple of lines from ltrace:
_ZNK24nsASingleFragmentCString19GetReadableFragmentER18nsReadableFragmentIcE17nsFragmentRequestj(0xbfffe160,
0xbfffe060, 1, 0, 0) = 0x4040e8e0
_ZNK24nsASingleFragmentCString19GetReadableFragmentER18nsReadableFragmentIcE17nsFragmentRequestj(0xbfffe160,
0xbfffe060, 3, 0, 0xbfffe160) = 0
_ZNK24nsASingleFragmentCString19GetReadableFragmentER18nsReadableFragmentIcE17nsFragmentRequestj(0xbfffe150,
0xbfffe060, 1, 0, 0) = 0x4040e8e5
_ZNK24nsASingleFragmentCString19GetReadableFragmentER18nsReadableFragmentIcE17nsFragmentRequestj(0xbfffe150,
0xbfffe060, 3, 0, 0) = 0
--- 0 (Real-time signal 0) ---
breakpointed at 0x42028828 (?)
breakpointed at 0x40444f57 (?)
_ZNK24nsASingleFragmentCString19GetReadableFragmentER18nsReadableFragmentIcE17nsFragmentRequestj
== nsASingleFragmentCString::GetReadableFragment(nsReadableFragment<char>&,
nsFragmentRequest, unsigned) const
(See comments on bug 144216)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Qt-Mozilla hangs on startup, before bringing up the UI. → Qt-Mozilla hangs in nsASingleFragmentCString::GetReadableFragment (?) on startup, before bringing up the UI.
Updated•23 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•23 years ago
|
||
Is this problem still an issue or can I mark the bug as WorksForMe (Qt build
2002-12-16-08-trunk starts up on my box without problems) ?
Updated•23 years ago
|
Whiteboard: [whitebox]
Assignee | ||
Comment 2•23 years ago
|
||
Assignee | ||
Comment 3•23 years ago
|
||
I am still wondering if is legal to call a nsAppShell event processing method
before nsAppShell::Run() was called - if the answer is "no" then the XUL code is
doing something wrong (since it hangs in |nsXULWindow::ShowModal()| without the
patch) - timeless ?
Blocks: qt
Summary: Qt-Mozilla hangs in nsASingleFragmentCString::GetReadableFragment (?) on startup, before bringing up the UI. → [Qt] Qt-Mozilla hangs in nsASingleFragmentCString::GetReadableFragment (?) on startup, before bringing up the UI.
Comment 4•23 years ago
|
||
firstly, thanks for your patch!
well, what does the code for other platforms do, does it use an approach like
this patch as well?
Attachment #111367 -
Attachment is obsolete: true
Updated•23 years ago
|
Attachment #111969 -
Flags: review+
checked in
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•