Bug 175680 – 40s when typing in #ifdef editor

HOME \ Community

Bug 175680 - 40s when typing in #ifdef editor

Summary:

40s when typing in #ifdef editor

Status:	RESOLVED FIXED

Product:	mobility
Component:	Build System
Version:	6.8
Platform:	All All

Priority:	P2 (vote)
Target Milestone:	6.8
Assigned To:	Petr Suchomel
QA Contact:	issues@mobility

URL:
Whiteboard:	perf-profileme
Keywords:	PERFORMANCE

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-10-29 16:26 by Jaroslav Tulach
Modified:	2009-11-11 05:51 (History)

Issue Type:	DEFECT
Exception Reporter :

Attachments
Profiler snapshot showing 40s in mobility editor code (71.63 KB, application/octet-stream) 2009-10-29 16:27, Jaroslav Tulach	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Jaroslav Tulach 2009-10-29 16:26:50

I've got an NPS file report via email. Here is excerpt from that mail:

After enabling self-profiling I have opened file with a class that contains a
lot of #ifdef/#if constructions and at 
the begining of the class I started to add following line:

  //#ifdef test

  //#endif

In case these lines are added at the end of the class, everything works OK.

------- Comment #1 From Jaroslav Tulach 2009-10-29 16:27:40 -------

Created an attachment (id=90221) [details]
Profiler snapshot showing 40s in mobility editor code

------- Comment #2 From Petr Suchomel 2009-11-06 09:56:56 -------

After recent chnages, performance is significantly better bu I am still trying
to improve it.

------- Comment #3 From Jaroslav Tulach 2009-11-11 04:10:21 -------

I tested the problem on build from Nov 3, 2009 and as far as I can tell the
problem seems to be fixed. I can type whatever (including //#ifdef) at begining
of the file without any noticable delays.

------- Comment #4 From Petr Suchomel 2009-11-11 05:51:03 -------

The bug is not reproducible after latest fixes