This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 146424 - FF3 - sometimes breakpoints not hit in php file url without restart
Summary: FF3 - sometimes breakpoints not hit in php file url without restart
Status: RESOLVED DUPLICATE of bug 146512
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-07 01:48 UTC by _ krystyna
Modified: 2008-09-12 02:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
sample project (2.21 KB, application/x-compressed)
2008-09-07 01:50 UTC, _ krystyna 		Details
original log (63.12 KB, text/plain)
2008-09-08 03:17 UTC, _ krystyna 		Details
reproduced log (22.45 KB, text/plain)
2008-09-08 03:18 UTC, _ krystyna 		Details
FF error console (137.85 KB, image/png)
2008-09-08 03:19 UTC, _ krystyna 		Details
screenshot (120.43 KB, image/png)
2008-09-08 03:20 UTC, _ krystyna 		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 _ krystyna 2008-09-07 01:48:46 UTC 
NetBeans IDE Dev (Build 20080906071253)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b13
System: Windows XP version 5.1 

I was able to reproduce this one time.
There seems to be some unreliability in FF3/Firebug

1. clean userdir 
2. set client-side only debug, firefox
3. unzip attached php project and run debug main
4. when r/o file url opens, pause, set breakpoints at javascript lines 1, 4, 8, 12, 16.
5. refresh browser
>breakpoints not hit; toolbar not activated

I once saw the stepping action after a project close and reopen but it does not 
always work. When I reproduced it, it required an IDE restart. I could never 
reproduce with a new userdir.
Comment 1 _ krystyna 2008-09-07 01:50:18 UTC 
Created attachment 69241 [details]
sample project
Comment 2 Quy Nguyen 2008-09-07 21:00:01 UTC 
If this is not easily reproducible, the IDE log and any info from the Firefox console would have been helpful.
Comment 3 _ krystyna 2008-09-08 03:15:26 UTC 
Attaching original logs and recently reproduced. One observation--had moved to client-side only debugging from multiple 
session. Will test that out.
Comment 4 _ krystyna 2008-09-08 03:17:23 UTC 
Created attachment 69268 [details]
original log
Comment 5 _ krystyna 2008-09-08 03:18:03 UTC 
Created attachment 69269 [details]
reproduced log
Comment 6 _ krystyna 2008-09-08 03:19:18 UTC 
Created attachment 69270 [details]
FF error console
Comment 7 _ krystyna 2008-09-08 03:20:24 UTC 
Created attachment 69271 [details]
screenshot
Comment 8 Quy Nguyen 2008-09-08 04:48:10 UTC 
It looks like something strange happens to Firefox if it isn't completely closed (all windows closed) between js
debugger sessions.  There is probably something in our Firefox browser extension that causes this behavior.
Comment 9 Quy Nguyen 2008-09-12 02:47:50 UTC 
Closing as duplicate, since it appears the root cause is the same.

*** This issue has been marked as a duplicate of 146512 ***