Issue 61123 - M152 - File Manager Locks While Typing In Path
Summary: M152 - File Manager Locks While Typing In Path
Status: CLOSED DUPLICATE of issue 60881
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m152
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0.2
Assignee: Frank Schönheit
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-24 19:14 UTC by drichard
Modified: 2006-02-23 11:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
gdb of crash when typing into file manager (1.14 KB, text/plain)
2006-01-24 19:15 UTC, drichard
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description drichard 2006-01-24 19:14:21 UTC
Tested on OOo 2.0.1 and works fine.  But in M152 I went in to configure my "My
Documents" directory.  File manager came up and instead of using the GUI, I
started to type in /users/drichard.   When I got to the "i" in drichard it
always locks and gdb revealed it's crashing.  Attaching gdb report.
Comment 1 drichard 2006-01-24 19:15:36 UTC
Created attachment 33529 [details]
gdb of crash when typing into file manager
Comment 2 drichard 2006-01-24 19:17:00 UTC
Confirmed that it happens in all places where file manager is used.  Seems to be
a bug related to autocomplete.
Comment 3 Joost Andrae 2006-01-25 10:02:28 UTC
JA: justified priority as it is a crash. This issue can be a duplicate to issue
60515. This needs to be clarified.

JA->TM: please leave this issue at your account until KSO has clarified who will
work on this. The issue is about a crash within the autocompletion within the
InetURL box in UCP file library.
Comment 4 kai.sommerfeld 2006-01-25 13:44:47 UTC
KSO->FS: The crash is caused by your recent changes in
svtools/source/control/inettbc.cxx (revision 1.4 => integrated m147). Under
certain circumstances SvtMatchContext_Imp instances get deleted twice which
leads to memory corruption.

Note: This one seems to be duplicate of #i60515#
Comment 5 Frank Schönheit 2006-01-25 13:56:13 UTC
known as (and fixed with) issue 60881. Fix will be part of 2.0.2.

*** This issue has been marked as a duplicate of 60881 ***
Comment 6 caolanm 2006-02-23 11:53:22 UTC
close as dup