joerg1985

@vfedirko5 i had a short look and from the stack i think your `WebElementWrapper` is the problem. There is no code to it, but i assume it extends `WebElement`, the...

@marcphilipp i am not refering to `testDisabled`, the feature request is about a new method `testSkipped` (or better `testBlocked`?) The way using the `TestExecutionListener` is possible and this is my...

@sureshg @Artem034 @BlueIce @DanmyWei @jmrg82 @vyarosh @simonovdenis @serrss @tcfurrer@xkamil @sbrannen @igor-dmitriev @sureshg You all liked (👍) the original feature so you might be interrested in this change to the feature?...

@sbrannen @marcphilipp i stumbled again into this issue for another project and for me it looks like this issue has some interrrest from the community. Would you like to discuss...

This would be nice, i have to delete the `source` type currently to get the `build` part only.

@goneall I don't think `both` is needed, you could just add a second `execution` to your pom to get both files.

@VietND96 i had a short look at the code of `EventBusCommand` and when looking at this (without debugging) i would expect a leak in the `/status` call. It adds a...

The leaking listeners have been fixed in https://github.com/SeleniumHQ/selenium/commit/269a7f6c11955b542d15396cef56699f7f31b811 but i am not sure this is the root cause here, as there are only a few bytes leaked for each call...

@Doofus100500 i think the best would be to create a heap histogram with [jmap ](https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/memleaks004.html) and share them here.

@Doofus100500 please wait for the next release before testing, this might be the fix for your issue: https://github.com/SeleniumHQ/selenium/pull/15011