Hmm, this looks like netbeans is doing something strange. I am not a netbeans developer so I can't help you with this.

But it's working fine with an older xdebug snapshots (middle of october). Should I still check this with the netbeans devs?

I don't know what that error could be, it could be that PHP/Xdebug crashes but you didn't mention anything like that. If that's the case, please provide a backtrace. See the following URL on how to do that:
http://bugs.php.net/bugs-generating-backtrace.php

Sorry, but there is no sign of php crashing. When I have the time I will try to figure out from which revision this behaviour starts.

If you can, please provide a short reproducable script, and a remote_log that contains only communications for a single debugging session. The one you provided contained many more.

Sorry about the old log, this one is slighty smaller. I made sure there was no previous xdebug.log before starting this session.

http://www.mediafire.com/?movjqnuvno5

I will try to create a short script.

I've put up a testcase here: http://www.mediafire.com/?mnmdnjkwwkm

I put a breakpoint on line 6. Then expand and view the contents of the $form variable. This seems to put netbeans in an infinite loop. It's causing a forever growing xdebug.log file and uses all cpu. So I will create a ticket for this over there.

From the logs it looks like netbeans runs "property_get" after the script has ended... don't know why, but that is what happens.

(I can see this clearly as a netbeans issues btw)